dev-cpp-users Mailing List for Dev-C++

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

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

Since it is a - at the most - 10 minute exercise, I don't think you need
to bother your examiner by complaining about lack of time.

/Per W

On Sat, 18 Oct 2003, Coosa wrote:

> Hi all,
>
>
>
> I had today a lab test in C++ and one of the 10 questions was to write a
> program which accepts a string input and reverse the words separately
> between spaces and outputs it to the stream. I couldn't solve it in time and
> I lost the marks for this section and went home and solved it.
>
> As a complain I want to know first, if this code could be simplified more as
> compact as possible, then write my lecturer a complain that the time wasn't
> enough to solve such questions, any way, the code is attached and working
> fine and I tried to make it as compact as possible, so please if some one
> can make it shorter, I'll be thankful.
>
>
>
> Best Regards
>
>
>
> Coosa
>
>
>
> Program output example:
>
>
>
> The words separated between spaces are isolated first and then reversed, not
> the entire string!
>
>
>
> Original Name  : This is a test!
>
> Reversed Name: sihT si a !tset
>
>
>
>