I thought that someone had suggested that the compression feature should be handled without any flags, but based upon configuration parameters and client headers.
The main reason for this is because you would have to do the checks anyway, does the compression library exist, can the client accept compression, etc. Then what do you do if compression is requested and it doesn't exist? Maybe this discussion happened over at OpenACS.org, but this is equivalent to an ssl layer, in general the application layer shouldn't get involved in this type of detail. tom jackson On Friday 11 April 2008 08:23, Dave Bauer wrote: > Dossy, > > I think the discussion is just this: > > As Bret clearly stated at the beginning of the thread: > > 1) modify ns_return to take a flag. The optional connid parameter > makes parsing the args a little trickier. > Current: > ns_return ?connid? status type string (is connid ever used??) > New > ns_return ?connid? status type string ?gzip? > OR > ns_return ?connid? status type string ?-gzip boolean? > > 2) add a new command similar to the workarounds: > ns_returnz status type string > > 3) Expose Ns_ConnSetGzipFlag to the script level. This would be most > similar to how the ADP compression is done > > I would like to see it but I don't forsee being able to write the code. > > Dave > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the > email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
