[xmlblaster-devel] SOCKET protocol support improved

[Marcel Ruff <ruff at swand.lake.de>]

Hi folks,

as more and more xmlBlaster users use the SOCKET protocol
instead of CORBA i have reviewed the code and fixed some
bugs.

   * The protocol specification changed to allow SOCKET messages without a
     MessageUnit
   * Bugfix: Distinguish between empty get() return and empty QoS as
     update return
   * Bugfix: Fail save mode of SOCKET did not propert callback
     Reported by Sebastian Sturm
   * Bugfix: Message where sometimes corrupted, during writing one message
     another mixed enbetween. Fixed with synchronize.
     Reported by Antti Jarvinen
   * Bugfix for blocking recursive remote invocations
     e.g. call publish() in update() body
     This is solved with a Thread per request approach on client side
   * Bugfix: Avoid blocking client thread on lost connection waiting
     for return value (freePendingThreads())


One feature added is a thread dispatch on client side for each
update() invocation.
Thus there is no deadlock situation anymore when in
an update() a recursive remote invocation (like publish())
is made, for more info see
   -socket.cb.multiThreaded
option in
 http://www.xmlblaster.org/xmlBlaster/doc/requirements/protocol.socket.html

enjoy

Marcel