RE: [Dev-C++] serialization question

[Nehal S. <ns...@ix...>]

Hi Dave-
 
So yeah handler is like a proxy between server and the client. There is some
mapping done on the handler side.
I have access of client side as well so I was thinking something like,
server will binary data to the handler and handler will convert it in such a
way that
some part of the data will be in ascii and some will be in bin. On the
client side I will do bare minimum process (which is must) in ascii and rest
will just use it in binary. So I guess that should work.
 
What do you think? you can send both data over one connection w/o any
problem so long as other side understand.
 
nehal
 

-----Original Message-----
From: David McKen [mailto:ci...@ya...]
Sent: Saturday, October 18, 2003 12:38 PM
To: Dev-Cpp Mailing List
Subject: Re: [Dev-C++] serialization question


Ok handler acts like a translator?
 
a simple handshake would work.
 
E.g.
<Connection Established to client that accepts binary data>
Handler: Hello 
Client: Hello, I accept binary data.
Handler: Very well I will send binary data.
<Continue connection using binary>
 

<Connection Established to client that does not ccepts binary data>
Handler: Hello 
Client: Hello 
Handler: <Assume the client does not accept binary>.
<Continue connection using ASCII>
 
Using this method the client tells the server whether it is capable of
accepting binary or not. The handler then sets up accordingly.
 
What are you capable of changing/updating? the clients, the handler or the
server? I do have another method but it requires changing the clients and
the handler.
 
Signed
David McKen
 

----- Original Message ----- 
From: Nehal Shah <mailto:ns...@ix...>  
To: dev...@li...
<mailto:dev...@li...>  
Sent: Friday, October 17, 2003 4:56 PM
Subject: [Dev-C++] serialization question


Hi All
 
 
I have a question regarding serialization out. So here is the current
working.
 
Client<---->handler<----->Server
 
in the current scenario whenever handler learns something from Server it
first (because it is in network order) decodes the data then serializes it
out and then spit it the client and and eventually client understands the
ASCII format.
 
 
In the new approach we are thinking of, not decoing anything at handler
level but just sending binary data to the client and on the client side they
will decode and store into the database.
 
now what I do not understand is, if my handler sends binary format to the
Client on the same connection on which sometimes client does accept the
ASCII data how is the client going to diffrenciate between those two and
what can I do to make it working in either case. 
 
 
Any suggestion/comments on this will be appreciate on this.
thanks



  _____  

Do you Yahoo!?
The
<http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext
%2Csec%3Amail> New Yahoo! Shopping - with improved product search