Re: [Dev-C++] serialization question
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
|
From: David M. <ci...@ya...> - 2003-10-18 19:39:21
|
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 To: 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 New Yahoo! Shopping - with improved product search |