Databases
StackOverflow2013
Postsdbo
POC# Sockets vs Pipes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC# Sockets vs Pipes
    primarykey
    data
    text
    <p>Currently I am working on a multi-process desktop application on Windows. This application will be a shrink wrapped application which will be deployed on client machines across the world. While we can have broad specifications for the machines - e.g. Windows XP SP3 with .Net 4.0 CF, we wont have control over them and we cant be too specific on their configuration - e.g. we cannot specify the machine must have a cuda 1.4 capable graphic processor etc.</p> <p>Some of these processes are managed (.Net 4.0) and others are unmanaged (C++ Win32). The processes need to share data. The options I have evaluated to date are </p> <ul> <li>Tcp sockets </li> <li>Named Pipes</li> </ul> <p>Pipes seem to perform a little better, but for our needs - performance from both are acceptable. And sockets give us the flexibility of crossing machine (and operating systems - we would like to support non-Microsoft OSes eventually) boundaries in the future hence our preference for going with sockets. </p> <p>However - my major concern is this - If we use Tcp sockets - are we likely to run into issues with firewalls? Has anyone else deployed desktop applications / programs that use TCP for IPC and experienced issues? If so - what kind?</p> <p>I know this is a fairly open ended question and I will be glad to rephrase. But I would really like to know what kind of potential problems we are likely to run into.</p> <p><strong>edit:</strong> To throw a little more light - we are only transporting a few PODs, ints, floats and strings. We have built a layer of abstraction that offers 2 paradigms - a request/response and subscription . The transport layer has been abstracted away and currently we have two implementations - pipe based and TCP based.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USquixver
    1. USquixver
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POC# Sockets vs Pipes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POC# Sockets vs Pipes
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POC# Sockets vs Pipes
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTo be clear, this is only on a single machine, so you're not using the named pipes to communicate between desktops? Or will there be some communication over the network as well?
      singulars
      1. POC# Sockets vs Pipes
      1. USKevin Anderson
    2. COFor now - all the processes are running on a single machine. Eventually - way down the road - we will be running the processes on different machines.
      singulars
      1. POC# Sockets vs Pipes
      1. USquixver
    3. COYou'll want to make sure you design for down the road :) Unless "way down the road" is theoretical ...
      singulars
      1. POC# Sockets vs Pipes
      1. USbryanmac
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload