David, Nicholas- Thanks much for the help. After being interested in POE::Component::IKC, I decided that was overkill for my application. I just went ahead and reused my publisher/subscriber code to pass a pointer to the data to any/all interested sessions.
-Craig On Apr 24, 2007, at 5:27 PM, David Davis wrote:
You may want to look at POE::Component::IKC http://search.cpan.org/~gwyn/POE-Component-IKC-0.1904/IKC.pod HTH Cheers David
On Apr 24, 2007, at 9:45 PM, Nicholas Perez wrote:
Pub/Sub is fine for this, but in the spirit of TIMTOWTDI... You could also have the IO portion read the data, parse it, dump it into a "shared" data structure, and have the GUI "refresh" either manually or with a(n) [alarm|delay]_set(). Or have them as two separate processes and have the GUI app connect via [IKC|HTTP|XMLRPC|JABBER|TCP|ETC] and pull the data down. Or have the GUI app act as the server and let the IO portion push to it and upon certain events update the interface. Or as a variation of the above, spawn the IO process as a child using POE::Wheel::Run and update the interface based on STDOUT from the child. Or, first, gather up all of the pants you can find. Second, ... Third, profit. :-D HTH
