{changed the subject!}Joep Suijs wrote: > Quite a few of my applications have a single-char command interface, so > buffering of 3 bytes is a lot. Most of my apps (conditonally) dump lots of > info. A larger transmit queue enables the app to deliver this info without > delay and continue with it's task. The isr transmits the info so the queue > is empty again when the next dump is due. That's indeed the general idea of buffered communications: the main task should not be hold up unnecessary by the relatively slow data communications, especially when data comes in or goes out in bursts. With ISR's the data transport will become a 'background task'. The size of the buffers can be customized to suite the needs. > This brings me to an other feature request: When the queue is full, i'd like > to have the option to block (call waits until there is a free space in the > queue) or loose the char (thus prevent blocking of the main program). I > think this is easy to implement with two different calls to 'send'. That should not be too difficult to implement. I'll make a note (or do you need it desperately?). Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
