0 Replies Latest reply on Oct 21, 2008 10:49 AM by dmlloyd

    (Extremely) Basic protocol implementation

    dmlloyd

      I've renamed the current "basic" to "multiplex" because that's really what it is, and made a real "basic" protocol. This protocol exists simply for testing and messing around; I don't want to produce any production configuration which uses this protocol. Basically it uses a single connection for each client rather than managing a multiplexed connection with service advertisement and so forth.

      This might be useful as a point of reference for the compatibility interface. I plan to use it to help me finish up the stream marshalling stuff. The one test fails with a security manager due to a bug in River, which has been fixed in that project's trunk.