It should be possible to send any size of "entire" message

[GoogleCodeExporter]

When reading a message from KBUS, an "entire" message is always returned
(if it tried to return a "pointy" message, life would be very unsafe).

When writing a message to KBUS, a "pointy" message of any size may be
written, but an "entire" message is limited in size. This is mainly because
it is much easier to cope with a "pointy" message inside the "write" mechanism.

This is excused because "pointy" messages are easier to generate in C, and
because it is always possible to "mock" an "entire" message as "pointy" (by
artificially setting the name and data pointers to the location of the name
and data in the "entire" message).

However, if one is reading data from KBUS, and reflecting it back again
(as, for instance, is done by Limpets), this begins to look silly. The user
should not be required to take extra-ordinary steps (viz, faking an
"entire" message as "pointy") just to make KBUS easier to implement.

Original issue reported on code.google.com by t...@tibsnjoan.co.uk on 10 Feb 2010 at 1:45

[GoogleCodeExporter]

Believed fixed in revision 303.

Note the C library API has replaced "_short_" function names with 
equivalent "_entire_" names (and updated the function header comments 
appropriately).

Original comment by t...@tibsnjoan.co.uk on 25 Feb 2010 at 2:34

• Changed state: Started

[GoogleCodeExporter]

Documentation and errno.py updated in revision 305 and 306 respectively.

Original comment by t...@tibsnjoan.co.uk on 25 Feb 2010 at 3:03

• Changed state: Fixed