I've got my communications across DO working and have been able to
pass large arrays from a *.dylib in C++ across. I'm just having a
blast with it.
So now Im wondering if it should be any problem that if I want my
thread to talk back to my server, is that ok? Or do I need to start
another connection going the other way? I'm thinking that if my server
connection hasn't been invalidated yet, it should still be good.
I want to do this so I can update my UI to show progress.
Comments, advice, suggestions, much appreciated.
Wizumwalt@gmail.com - 25 May 2007 04:53 GMT
Or does anyone know of any example source where DO communicates both
ways between two threads?
I've got one way working, but can't updated my UI from the worker
thread.
Any help much appreciated.
Patrick Machielse - 25 May 2007 10:46 GMT
> So now Im wondering if it should be any problem that if I want my
> thread to talk back to my server, is that ok? Or do I need to start
> another connection going the other way? I'm thinking that if my server
> connection hasn't been invalidated yet, it should still be good.
Yes, you can just pass 'self' when messaging the remote process /
thread, and the receiver can use that reference / proxy to call back, as
long as the connection is valid. If the receiver never needs to initiate
a connection, there is no need to vend 'self', although you still could,
of course.
patrick