Subject: From: Date:

RE: [ECS] Socket Connection Nathan Brown Sun, 7 Jan 2001 21:36:26 -0800

---

 Sun, 7 Jan 2001 21:36:26 -0800
My original request was targeted more at being able to write additional
services that ECS could connect to and make requests from, NOT for high
level protocol requests.  If you want to put higher level protocols into
ECS that would be a different need entirely that to be able to make
protocol independent socket requests.  Perhaps it would help if you
detailed your need for this type of enhancement.

NB

-----Original Message-----
From: Ingo Pakleppa [mailto:ipakleppa@yahoo.com]
Sent: Sunday, January 07, 2001 7:13 PM
To: ecs-list@netbloc.com
Subject: Re: [ECS] Socket Connection


At 11:02 PM 1/7/2001 +0100, Dario Greggio wrote:
>As for binary data, unless we want to deal directly with them (that is,
>build binary data on our own), a solution I've found is to look for
such
>files on the hard disk: this way, you may send images or sounds to the
>client without having to open and handle them.

Well, the point I was trying to make is that quite often, if you just
open 
a binary file and send it, the protocol won't be able to handle it. You
may 
have to first translate it into ASCII characters using something like 
Base64 encoding or UUEncode.

Of course I may well be quite off base on this. Personally, I have no
need 
for TCP/IP; I'm just looking at the request from a software engineering 
standpoint.

Ingo

---