Hi John,
As i understand, Alexandre wants to get rid of the service thread completely. He rejected an async i/o patch of mine that used the service thread on these grounds.
The server would also need to wait on the service thread somehow... something else that might be frowned upon.
i'm pretty sure that currently there isn't any way to do this except use the service thread though :-(
Perhaps it'd be nice to tie up all these memory issues with some kind of kernel patch... a way to read/write and generally mess with another process's memory that was broader and more efficient that p-trace.
Mike
Is there any reason _not_ to use the service thread of the target process to perform cross-process ? virtualAlloc/Protect etc?
Jon
------------------------------------------ mailto:Mike_McCormack@looksmart.com.au ph +61 2 9427 2196
__________________________________________________________________ Get your own free web email at http://www.looksmart.com.au LookSmart Australia
Hi,
Perhaps it'd be nice to tie up all these memory issues with some kind of kernel patch... a way to read/write and generally mess with another process's memory that was broader and more efficient that p-trace.
Something like that would be great for Linux, not sure how it could work with closed unices though. I've been trying to figure out the server and it does't look like anything currently implemented does anything like I wanted to do, so you're right, it probably wouldn't get accepted even if it could be used.
Maybe I'll find something else to dabble with for now :-/
Cheers, Jon