> -----Original Message----- > From: Matt S Trout [mailto:[EMAIL PROTECTED] > On Wed, Nov 02, 2005 at 10:10:47AM -0800, Gil Vidals wrote: > > I'm hoping someone can point me in the right direction. I'm stuck on > > figuring out how to handle the situation where session A initiates a TCP > > client session B; however, by the time TCP session B is ready to do it's > > thing, session A is way ahead and session B is now lost without the data > > from session A. > > How about having session A store the data into a buffer as it reads it, > and then when session B's started is says to session A "I'm ready now, > give > me the contents of the buffer and start sending me stuff in real time" ?
I'm no expert here, but I ran into a similar problem with the IRC Component. My code block would finish before the actions it started had happened. I solved my problem by using a ->call() instead of a ->yield(). As I understand it, doing a ->yield() just posts the message into the queue, and code continues unchecked, but doing a ->call() blocks until the command returns. Maybe this would work for you too, Gil? Regards, Gavin McDonald ======================== EVI Logistic Enterprises email: [EMAIL PROTECTED] phone: (604) 313-3845>
