Recent Activity

  • Ionuț shared from a Personal Document
    Backward-compatible changes are ones that are safe to add to the media type design without adversely affecting future implementations.
  • Ionuț shared from a Personal Document
    Forward-compatible design changes are ones that are safe to add to the media type without adversely affecting previously existing implementations.
  • Ionuț shared from a Personal Document
    In cases where the media type design is not Domain-Specific, additional information will be needed in order for clients and servers to share proper understanding of the messages passed between them. This additional information is sometimes called Domain Semantics or Application-Level Semantics. This added semantic information can be documented, and that documentation can be used when implementing client and server applications that will use the media type to which the semantics are applied.
  • Ionuț shared from a Personal Document
    I have the world’s largest collection of seashells. I keep it on all the beaches of the world; perhaps you’ve seen it. - Stephen Wright
  • Ionuț shared from a Personal Document
    Hypermedia type designs for automated services (bots, machine-to-machine interactions, etc.) are a good candidate for designs that do not contain application flow identifiers.
  • Ionuț shared from a Personal Document
    For human-driven clients, ad-hoc state transfers can be handled by rendering the inputs and waiting for activation. However, for clients that have no human to intervene, the ad-hoc style can be an added challenge. If your primary use case is for automated client applications, the ad-hoc state transfer style may not be the best design choice.
    Note: Hah!
  • Ionuț shared from Java Concurrency in Practice by Tim Peierls, Joseph Bowbeer, Joshua Bloch, Brian Goetz, Doug Lea, David Holmes
    Interruption is a cooperative mechanism. One thread cannot force another to stop what it is doing and do something else; when thread A interrupts thread B, A is merely requesting that B stop what it is doing when it gets to a convenient stopping point—if it feels like it. While there is nothing in the API or language specification that demands any specific application-level semantics for interruption, the most sensible use for interruption is to cancel an activity. Blocking methods that are responsive to interruption make it easier to cancel long-running activities on a timely basis.
  • Ionuț shared from Java Concurrency in Practice by Tim Peierls, Joseph Bowbeer, Joshua Bloch, Brian Goetz, Doug Lea, David Holmes
    The Java Memory Model requires fetch and store operations to be atomic, but for nonvolatile long and double variables, the JVM is permitted to treat a 64-bit read or write as two separate 32-bit operations. If the reads and writes occur in different threads, it is therefore possible to read a nonvolatile long and get back the high 32 bits of one value and the low 32 bits of another.
  • Ionuț shared from Java Concurrency in Practice by Tim Peierls, Joseph Bowbeer, Joshua Bloch, Brian Goetz, Doug Lea, David Holmes
    Thread safety may be a term that is applied to code, but it is about state, and it can only be applied to the entire body of code that encapsulates its state, which may be an object or an entire program.
    Note: Thread safety
  • Ionuț shared from Programming in Scala: A Comprehensive Step-by-Step Guide by Martin Odersky, Lex Spoon, Bill Venners
    Marking Rule: Only definitions marked implicit are available.
    Note: Why not import site marking? #scala
(Bucharest, Romania)
Ionuț G. Stan
Web Page: http://igstan.ro