Yeah the project "BasicCommandServer" actually looks quite interesting.
Saves "ME" having to parse the data :-)

Jeremy

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Phil Middlemiss
Sent: Thursday, 15 April 2004 11:21
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] TCP/IP or MailSlot?


Jeremy, I would recommend going with TCP/IP. The Indy components make
this a snap (Heck, the demo code is 90% what you need) and you keep your
future options open for more complex transfers of information, security,
etc etc.

Phil.
----- Original Message ----- 
From: "vss" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 15, 2004 9:19 AM
Subject: [DUG] TCP/IP or MailSlot?


> Hi all.
> I have a need to send data from one app to another which mcan be on 
> the
> same machine or on another PC.
> Our prediction is, that 95% of the time both apps wil beon the same 
> machine.
> I am wondering, are Mailslots robust enough for this? or would I need
to 
> use TCP/IP.
> I am only passing text, and its not complex structures etc.
> 
> I did wonder about using DCOM but it mightbe overkill for this 
> situation.
> 
> Cheers Jeremy
> 
> _______________________________________________
> Delphi mailing list
> [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
> 
_______________________________________________
Delphi mailing list
[EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi



_______________________________________________
Delphi mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/delphi

Reply via email to