node.js is a tcp server / client.
On Sat, Nov 26, 2011 at 4:29 PM, Anthony Mayan wrote:
> Need to talk between ubuntu and windows server.
>
>
> On Wed, Nov 23, 2011 at 6:36 PM, Greg Keogh wrote:
>
>> Want to avoid creating a multi-thread tcp listener to handle all the
>> connections...anyone h
Need to talk between ubuntu and windows server.
On Wed, Nov 23, 2011 at 6:36 PM, Greg Keogh wrote:
> Want to avoid creating a multi-thread tcp listener to handle all the
> connections...anyone have an suggestions?
>
> ** **
>
> Assuming you want duplex communication ... if you plan to run i
Want to avoid creating a multi-thread tcp listener to handle all the
connections...anyone have an suggestions?
Assuming you want duplex communication ... if you plan to run inside the LAN
where Remoting can open callback channels, the Remoting is old but reliable.
A singleton server handles inc
et.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Jano Petras
> *Sent:* Tuesday, 22 November 2011 6:53 PM
> *To:* ozDotNet
> *Subject:* Re: Client /Server alternative for TCP
>
> ** **
>
> Well, hosting you application under IIS would get rid of worries
otNet
Subject: Re: Client /Server alternative for TCP
Well, hosting you application under IIS would get rid of worries regarding
listeners and connections, if your system needs to follow regular REST
request/response pattern (that is, you don't need to keep the connection
open).
WCF is
Well, hosting you application under IIS would get rid of worries regarding
listeners and connections, if your system needs to follow regular REST
request/response pattern (that is, you don't need to keep the connection
open).
WCF is an option here as it supports REST, or - just plain ASP.NET or M
