Hi,
I'm looking at getting conditional GETs going with the SkillsBase application. I'd like to introduce a HTTPHeaders class to represent the collection of header fields in a message, and have a class for each of the conditional header field types. This is all to make it easier to handle in my app, of course :-) In the course of doing this, I'm refactoring some of the request parsing code, and I have a question about something in there: Does anyone know what purpose the contentsStream in a message serves? It looks like this is a kind of copy of the message created as the message is read in and parsed, but I can't see anything using this contentsStream once it's created. I'm planning to drop it from the version I'm working on unless I hear a howl of protest (with a reason :-) ) from someone. Thanks, Bruce -- Make the most of your skills - with OpenSkills http://www.openskills.com signature.asc (227 bytes) Download Attachment |
Hi Bruce,
Bruce Badger pravi: > Hi, > > I'm looking at getting conditional GETs going with the SkillsBase > application. I'd like to introduce a HTTPHeaders class to represent the > collection of header fields in a message, and have a class for each of > the conditional header field types. > > This is all to make it easier to handle in my app, of course :-) > I think you are doing extension for a "common good" so go ahead ;) > In the course of doing this, I'm refactoring some of the request parsing > code, and I have a question about something in there: > > Does anyone know what purpose the contentsStream in a message serves? > It looks like this is a kind of copy of the message created as the > message is read in and parsed, but I can't see anything using this > contentsStream once it's created. I'm planning to drop it from the > version I'm working on unless I hear a howl of protest (with a reason > :-) ) from someone. > that sending a response goes in one step and not in many many small fragments, which slows response time over slow links singnificantly. I will publish my branch of Swazoo on Cincom public repository soon and I propose that you and others do the same. After merging I think it is more than a time for Swazoo v1.0 and not 0.9.x anymore, what do you think? Best regards Janko -- Janko Mivsek Systems Architect EraNova d.o.o. Ljubljana, Slovenia http://www.eranova.si |
On Mon, 2004-08-02 at 20:19, Janko Mivšek wrote:
> Bruce Badger pravi: > > This is all to make it easier to handle in my app, of course :-) > > > I think you are doing extension for a "common good" so go ahead ;) Off I go, then! > > > In the course of doing this, I'm refactoring some of the request parsing > > code ... > > > I did some refactoring of that code too by introducing another buffer so > that sending a response goes in one step and not in many many small > fragments, which slows response time over slow links singnificantly. > > I will publish my branch of Swazoo on Cincom public repository soon and > I propose that you and others do the same. After merging I think it is > more than a time for Swazoo v1.0 and not 0.9.x anymore, what do you think? often, so you'll see some of my work already there. I'll post here when I publish this set of changes. All the best, Bruce -- Make the most of your skills - with OpenSkills http://www.openskills.com signature.asc (227 bytes) Download Attachment |
Free forum by Nabble | Edit this page |