JLS Quote: "If S is a class type: ... If T is an interface type: ... If S is not a final class (�8.1.1), then the cast is always correct at compile time (because even if S does not implement T, a subclass of S might). If Swampthing were to be a final class it would resu,t in a compile time error.
Ade, Connection-less protocol like say UDP doesn't by itself provide a reliable transport. However, you can build application layer protocol over UDP that provides this reliability. Your example of ESRO Protocol is built over non-reliable connectionless transport UDP. The reliability aspect is handled by ESRO Protocol and not by the underlying transport layer. Likewise WTP also runs over an connectionless unreliable datagram transport layer.
Ade, Connection-less protocol like say UDP doesn't by itself provide a reliable transport. However, you can build application layer protocol over UDP that provides this reliability. Your example of ESRO Protocol is built over non-reliable connectionless transport UDP. The reliability aspect is handled by ESRO Protocol and not by the underlying transport layer. Likewise WTP also runs over an connectionless unreliable datagram transport layer.
------------------------------------------------------------ I also learned that HTTP spec does not require it to be implemented on top of a connection oriented transport layer. ------------------------------------------------------------ Are you sure about that ? The RFC says HTTP MUST be implemented over a Reliable Transport Layer. Does a Connection less protocol provide a reliable transport layer ? I guess NO.
------------------------------------------------------------ I also learned that HTTP spec does not require it to be implemented on top of a connection oriented transport layer. ------------------------------------------------------------ Are you sure about that ? The RFC says HTTP MUST be implemented over a Reliable Transport Layer. Does a Connection less protocol provide a reliable transport layer ? I guess NO.
Patrick, Yes, it is possible to nest jar files. But then in the Classpath of the Manifest of the root jar you have to specify the relative path to the inner jar files. Not sure if that answers your question, Hope this helps.
JL Spec says The notify method should be called for an object only when the current thread has already locked the object�s lock. If the wait set for the object is not empty, then some arbitrarily chosen thread is removed from the wait set and reenabled for thread scheduling. So for the program to hang the wait set for the object should be empty at the time when notify is called.
Gopal In C++ this happens due to object slicing. When you pass ploymorphic objects by value they get sliced. Since you are left only with the base class part you see the base class version of the method getting invoked.
