it's certainly possible, and probably the easiest way. using local sockets doesn't take much in the way of resources, and provides an alternate synchronization/serialization paradigm for you so you can avoid a lot of the messiness with concurrent programming. plus it's easily cross-platform compatible, and distributable if you ever want to run the two modules on separate machines.

my only suggestion would be to consider udp instead of tcp, since you don't need a lot of the junk tcp provides when you're not actually going out over a potentially lossy network.

best regards, r.

Yeah David, Richie is right - I think using UDP packets to communicate between processes is pretty standard.

Ben

Thanks for the feedback. I had some code from another project using tcp/ip which I thought I would just modify, but I'll look into UDP also as you advise. Thanks, David.