> Ask Marc at Aliacta .... it can be done but it's a fair bit of work. Yeah... a substantial amount of work...
If I understand Guillermo, the way pgSQL4RB works isn't what he wants though. He literally wants no code execution while waiting for a result, yet without wasting CPU. pgSQL4RB however does allow code execution while waiting for a result, even sending of more queries. (Yet with each result arriving in a totally orderly fashion.) I believe he has no option but to use Poll and settle with the CPU cycles that are needed for this. There's no other way to stop code execution while waiting for the result that I'm aware of with TCPSockets. Without Poll he can't write sequential code and he'd have to switch to event based code. I believe he's after sequential code. Ultimately, if he writes something like a database, all steps need to be performed one by one anyway by the back-end for the sake of the data's integrity (this is a highly simplified representation of course, unrelated or read-only activities could be done 'simultaneously'). Marc _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
