On Oct 26, 2006, at 10:24 PM, David Blevins wrote:
My first thought was to enhance the OEJP to support "headers" like
HTTP does and then use the "keepalive" idea. I bumped up the OEJP
version to 2.1 so that the client/server would know to check for
the existance of headers in the request/response. The marshalled
headers would be in the format of:
Existing structure: [OEJP/2.0][request-id][request-data]
New structure: [OEJP/2.1][#-of-headers][headers][request-id]
[request-data] where headers is [len][name-data][len][value-data]
This saved, combined with socket pooling, approx. 34%
My second thought was to avoid the NVP headers and use a byte
array of bit flags, the new format is:
[OEJP/2.1][byte-of-flags][request-id][request-data]
This is 27% faster then my first thought.
Can you give more info on the byte approach? Not grokking why it's
slower than bytes of "string" data
What is the nature of your NVP? What would be the data type of the
name and of the value?
Any thoughts?
-David
