wai-logger v0.0.1
Hello, I have released wai-logger v0.0.1. - This version removes the date thread. Instead new cache mechanism suggested on this ML was implemented. - This version still uses Data.Time. This is because C's strftime did not contribute to improve performance according to my benchmark. - Experimental APIs for Builder are provided: apacheFormatBuilder and hPutBuilder. These APIs are slower but will be revisited when new ByteString library will become available. --Kazu
Thanks a lot, Kazu! This is a great building block for any web framework. We
are going to make sure it integrates well with Yesod, although not
necessarily with the 0.9 release that we already have a release candidate
for.
On Tue, Aug 23, 2011 at 8:32 PM, Kazu Yamamoto
Hello,
I have released wai-logger v0.0.1.
- This version removes the date thread. Instead new cache mechanism suggested on this ML was implemented.
- This version still uses Data.Time. This is because C's strftime did not contribute to improve performance according to my benchmark.
- Experimental APIs for Builder are provided: apacheFormatBuilder and hPutBuilder. These APIs are slower but will be revisited when new ByteString library will become available.
--Kazu
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel
Greg,
Thanks a lot, Kazu! This is a great building block for any web framework. We are going to make sure it integrates well with Yesod, although not necessarily with the 0.9 release that we already have a release candidate for.
Please check if we can make wai-logger as a WAI middleware. In my opinion, it is possible if we change WAI a bit. But I guess people do not want to change WAI. --Kazu
On Thu, Aug 25, 2011 at 4:40 AM, Kazu Yamamoto
Greg,
Thanks a lot, Kazu! This is a great building block for any web framework. We are going to make sure it integrates well with Yesod, although not necessarily with the 0.9 release that we already have a release candidate for.
Please check if we can make wai-logger as a WAI middleware. In my opinion, it is possible if we change WAI a bit. But I guess people do not want to change WAI.
Hi Kazu, It's not that I'm opposed to changing WAI, but if I know the change you're referring to (changing ResponseEnumerator), it probably won't happen. ResponseEnumerator was designed the way it is specifically to allow things like proxy servers, where you don't know the status code or headers until you've initiated the response enumerator. I still think it will be possible to implement the API you're hoping for with the current WAI. Do you want to sketch out the initial work and then be in touch with me so we can develop it more fully? Michael
Michael,
It's not that I'm opposed to changing WAI, but if I know the change you're referring to (changing ResponseEnumerator), it probably won't happen. ResponseEnumerator was designed the way it is specifically to allow things like proxy servers, where you don't know the status code or headers until you've initiated the response enumerator. I still think it will be possible to implement the API you're hoping for with the current WAI. Do you want to sketch out the initial work and then be in touch with me so we can develop it more fully?
It was Greg that asked me to implement a log system as a middleware. I think it's nice if we can implement such a middleware. But it's not my hope, it is Greg's hope. If people satisfy with the current wai-logger, it's enough to me. --Kazu
participants (3)
-
Greg Weber -
Kazu Yamamoto -
Michael Snoyman