Re: [Siop-development] SIOP FAQ

[Rapheal K. <ra...@ma...>]

>   I would like to see something like that happen.  So far, for some Python
> like reason, I am not able to hook up callbacks to wxWindows, although
> callbacks in general work over SIOP.  Maybe the wxPython has a wierd way of
> handling setattr.
>
>   This Ruby code works so far - When I figure a few more things out I will
> document it on the Wiki...
>


  Of course... a windowing system IMMEDIATELY has threading issues.  The call 
backs are coming in on a different thread, the results are returning from the 
Python server out of order.  So, now there are threading issues.

  I though about having each message pass through with a sort of call stack 
identifier.  As long as the transport itself is multi-threaded, it should be 
possible to have multiple threads with multiple call stacks using the bridge.