Greg Borenstein wrote:
I may be totally off base here as much of the technical discussion
involving details of how gui toolkits normally handle this stuff is over
my head, but could you maybe handle your situation by using queues to
tie things together? For example, beanstalkd is a solid, scalable
queuing implementation with a good ruby front end:
http://xph.us/software/beanstalkd/
If you had one queue between each pair of processes (log parsing <-> sql
lite, sql lite <-> shoes) your consumer could just pull of the new
messages from the queue at its own rate without having to block waiting
on the other process to answer a query and without having to deal with
the complexity of spawning additional threads.
Is this on the right track at all?
Absolutely.
Threads are like goto.
