Hello to everybody. I agree that I can use the specification to discover the syntax of the exchanged data. Its semantics, however, can not be exactly understood only by watching those data. In effect, I really need of the protocol specification.
For example, there is a message that contains only four bytes, named 00 00 00 01. Are those bytes related to the number of version of discovery protocol? I guess, but I am not sure about it. By the way, the protocol specification present on JINI pages does not contains anything about it, because it is related to the reference implementation, not to the standard itself... I also agree that the bandwidth comsuption will be defined by communication between client and service. But I still believe that it is interesting to know how much bandwidth is comsumed during that setup phase. Well, I will watch the java serialization object specification. When I find some interesting stuff, I will post it on forum. Kindest regards to all, gentlemen. Helcio. 2010/3/26 Sim IJskes - QCG <s...@qcg.nl>: > On 03/26/2010 06:32 PM, helcio silva wrote: >> >> When watching the JINI protocols specification, I didn't find any >> information about I exposed above. > > You really need to read: Java Object Serialization Specification; Object > Serialization Stream Protocol. > > With this specification and the class source files from jini, you can decode > all the data you've captured. > > Gr. Sim > > > >
