isnt serial comms done with readwrite on /dev/serialdevice or something? although that is a good idea to write a Driver for serial comms.
On 12/5/06, Nicholas Perez <[EMAIL PROTECTED]> wrote:
I guess it would help if I copied the list... ---------- Forwarded message ---------- From: Nicholas Perez <[EMAIL PROTECTED]> Date: Dec 5, 2006 11:17 PM Subject: Re: Serial communications To: lanas <[EMAIL PROTECTED]> My two US$0.02: Write a configurable Filter (make meaningful objects from input). Write a configurable Driver (handle all the nasty flow control etc here). Then add those two things into a generic Wheel::ReadWrite. And then it is trivial to write a POE::Component that uses these things to cut out some of the tedium. For all the low level serial stuff, I would probably reference one of the serial modules for how they do it, and then adapt it into a more POE-ish way of thinking. This way you get the benefit of reuse (sort of), and the benefit of NOT trying to shoe-horn in a blocking beast of code. As long as you meet the interface requirements of POE::Driver, you are pretty much free to do whatever it takes. On 12/5/06, lanas <[EMAIL PROTECTED]> wrote: > Folks, > > Recently I've asked about serial communications. If I'd like to add > serial communications support to POE, what would be the best way to do > this ? By using an existing Perl module and wrapping around it or by > writing serial comms from scratch ? > > (You may file that as a meditative question... ;-) > > Cheers, > Al >
