> > (Assuming that indeed there's no way of using sockets in a non-blocking > fashion - I'm totally ignorant about that) maybe having a little process > created with multiprocessing would be simpler & more portable, for you, > than using threading? I guess a single one is sufficient, so the > overhead shouldn't be significant, even on Windows. Then, at every > iteration of the main loop, the main process could check, from a shared > Value (or Array), if there's something to open. > > (untested, sorry if I wrote something stupid) >
Hi Pietro, the problem of having a single and independent process dedicated to the job of server is that the server would not be able to rise a minimized/hidden window as consequence of the situation "a new file open starts (user double click) unaware that the same file is already opened". Best regards, Giuseppe.
_______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
