I think I would agree with you, if I change your wording slightly: "The application should [have the ability to] "hint" to the server when compression might be appropriate for a response."
I think in most scenarios, the config params should be good enough for deciding on when to compress, however, having the ability to add a decision point in the application code I think is worthwhile, and gives the developer a lot of flexibility. For *my* application, I would have the config params do the decision almost all of the time. However, I concede that other people's use cases may be different...so I think a hook into the compression decision making from application code is a good idea. I believe what I proposed covers the bases...although the details would need to be worked out... ----- Original Message ---- From: Dossy Shiobara <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, April 12, 2008 6:55:53 AM Subject: Re: [AOLSERVER] Compression On 2008.04.11, Tom Jackson <[EMAIL PROTECTED]> wrote: > If folks keep anything in mind it should be that applications should > not deal with I/O performance details, at least in AOLserver. > AOLserver is an application server, which means that it serves the > application, the application doesn't serve anything. This is why compression was implemented the way it is for ADPs. The application should "hint" to the server when compression might be appropriate for a response. But, the server is ultimately responsible for determining if compression can happen, doing the compression and handling the I/O. > It isn't an easy concept, and it shouldn't be handled by modifications > to the ns_return API. Which is why I suggested ns_return_compress, similar to ns_adp_compress but for ns_return'ed responses. -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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.
