blue box + raw protocol problem

Submit all your BlueBox related questions or report a bug here!

Moderators: Lapo, Bax

Post Reply
Boing
Posts: 59
Joined: 11 Apr 2008, 14:57

blue box + raw protocol problem

Post by Boing »

Hi everyone,

in our application we are using the raw protocol for some client/server communication. The transmitted data is of a very special format and can basically contain any character (with which I mean all 256 bit combinations) except "all bits zero". This works perfectly with a socket connection. But through the blue box in special cases the client receives other data than by using the socket.

As far as we have figured out so far these special cases have something to do with the first character being of value 10 (line feed) which seems to be replaced with value 32 (white space) when arriving at the client.
Does jetty perform this replacement?

Any hints on this problem?
User avatar
Lapo
Site Admin
Posts: 23438
Joined: 21 Mar 2005, 09:50
Location: Italy

Post by Lapo »

Yes, you cannot use the LF character which is used internally to separate multiple messages.
Lapo
--
gotoAndPlay()
...addicted to flash games
Boing
Posts: 59
Joined: 11 Apr 2008, 14:57

Post by Boing »

Thanks for the answer.
As long as this is the only restriction we can live with that.

Just to be sure: Character value 0 and 10 are the only forbidden ones?
User avatar
Lapo
Site Admin
Posts: 23438
Joined: 21 Mar 2005, 09:50
Location: Italy

Post by Lapo »

Correct
Lapo
--
gotoAndPlay()
...addicted to flash games
Boing
Posts: 59
Joined: 11 Apr 2008, 14:57

Post by Boing »

Cheers.
Post Reply