Roland et al, One of the complaints about HttpCore API we have been unable to resolve so far is an asymmetry between the process of entity serialization (represented by the EntityWriter interface) and that of entity de-serialization (represented by the EntityGenerator interface) was . Presently, EntityWriter is not meant to make any modification to HTTP messages in order to ensure the exact details of the content transfer mechanism being utilized is correctly communicated to the opposite side of the protocol. The EntityWriter interface implicitly assumes all relevant HTTP headers are taken care of elsewhere. This approach, of course, implies that the failure to provide the required protocol interceptor or, worse, to keep in sync implementation of the EntityWriter and the corresponding protocol interceptor will break HTTP connection.
I would like to suggest the following changes: (1) Rename EntityWriter to HttpEntitySerializer and EntityGenerator to HttpEntityDeserializer (I am open to different (better) names). (2) The HttpEntitySerializer will be required to set (override if needed) the 'Transfer-Encoding' and 'Content-Length' headers to ensure the integrity of the underlying HTTP connection Any objections to that? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
