Re: Sockets for inter-process communication
> Is this terribly inefficient? What I mean is - using a network socket to
> exchange objects with another app or thread on the same machine.
Have you actually looked into this at all?
On most systems I know of, a socket to the local machine (i.e 127.0.0.1,
etc) never even hits the ethernet hardware. It just stays in memory and
gets bumpped around a little.
I've even seen bugs exposed because running the client and server both
on the same machine suddenly makes stuff waaaaaay faster.
|All times are GMT. The time now is 09:11 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.