2008/9/24 Rob Hamerling <[EMAIL PROTECTED]> > >If that is worth the risc of buffer overflow will depend on the > >characteristics of the communication.
I'm afraid I have to quote you on that one ;-) Different applications have different requirements. 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. 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'. Joep --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
