IPC and other system dependent functionality was probably added to Qt, because C++ standard library lacks it. But, since Python has powerful crossplatform standard library and lot of free packages, I'm not sure you should use PyQt for your IPC. It is often good idea to divide GUI and core functionality. Try looking at Python native libs.
Best Regards, Andrei Kopats 2011/10/25 zw g <pekingmas...@gmail.com> > Thank you David. > > Yes, i need the cross-platform feature. > > And yes, i controlled both ends of the communication, and each app has it's > own GUI window. > All my want is send some messages from one side to another, to let the > target one do some internet searching thing then display the result on it's > UI. > > More suggestion? > Thanks all the time. > > > Gui > > > > On Tue, Oct 25, 2011 at 5:30 AM, David Boddie <da...@boddie.org.uk> wrote: > >> On Sat, 22 Oct 2011 10:00:43 +0800, zw g wrote: >> >> > Could someone tell me that what is the best or recommended approach to >> do >> > the IPC(Inter-Process Communication) thing? >> > >> > QProcess? >> > QSharedMemory? >> > Or just socket? >> >> It depends on how your application works, whether or not you want a >> cross-platform solution, and what other applications you will be >> communicating with. >> >> If you control both ends of the communication, all of the above will work. >> There are Qt examples for these, and some of these may have been ported to >> Python. >> >> There is also D-Bus for Unix/Linux applications. >> >> David >> _______________________________________________ >> PyQt mailing list PyQt@riverbankcomputing.com >> http://www.riverbankcomputing.com/mailman/listinfo/pyqt >> > > > _______________________________________________ > PyQt mailing list PyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt >
_______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
