search

berkus / kbus

Automatically exported from code.google.com/p/kbus
Other
1 stars 0 forks source link

KSock ids need to contain a network id #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Consider use of Limpets to allow communication between different KBUS 
devices (on the same machine or different machines).

Then consider trying to do a stateful transaction (see http://
kbus.googlecode.com/svn/trunk/docs/_build/html/docs.html#id31) through 
such a bridge.

Since the user is not expected to be able to tell which apparent 
connections use Limpets to mediate the message passing and which do not, 
we cannot expect stateful transactions to work for non-Limpet systems and 
not for those using Limpets.

Thus stateful transaction must work through Limpets. But when we are 
sending a message through a Limpet, it currently replaces the originators 
KSock id with that of the Limpet forwarding the message. There is no way 
of producing a useful mapping through this narrowing of information.

This needs resolving now, not so much because we need stateful 
transactions now, but more because we do not want to change KBUS message 
datastructures after the next major release.

Original issue reported on code.google.com by t...@tibsnjoan.co.uk on 27 Jan 2010 at 5:07

GoogleCodeExporter commented 9 years ago 
Believed fixed (in at least a preliminary form) with the development
of Limpets and the new (longer) KBUS message header.

Revision 295 has all the fixes and documentation updates, although some 
tidying up (particularly of kbus_defns.h) and some more writing of 
documentation is still needed.

Original comment by t...@tibsnjoan.co.uk on 21 Feb 2010 at 11:39