I'm considering porting Erlyweb to use ewgi to loosen the coupling with yaws. As I see it there are 2 main touch points between Erlyweb and yaws:
* yaws_args/yaws_headers - This looks pretty straightforward. We'd just need to replace yaws api calls with the corresponding ewgi calls. ewgi appears to be missing cookie support in ewgi_api but I think I could add that. Does this sound about right? * erlyweb:out/1 -- I'm hung up on this one and looking for some ideas. Yaws calls this function directly for each request. Does ewgi have something we could shim in here in its place? I'm thinking of some sort of appmod that proxies yaws calls into Erlyweb. --Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
