Kevin A. Smith wrote: > > On Jan 3, 2008, at 3:44 PM, Adam Bozanich wrote: > >> On Jan 3, 2008 10:42 AM, Yariv Sadan <[EMAIL PROTECTED]> wrote: >> >> On Jan 3, 2008 3:32 AM, Filippo Pacini <[EMAIL PROTECTED]> >> wrote: >> >>>> * yaws_args/yaws_headers - This looks pretty straightforward. We'd >>>> just need to replace yaws api calls with the corresponding ewgi >> calls. >>> This should be easy. >>> A problem might be ewgi missing support for yaws opaque data. Is it >>> required from erlyweb? >>> A solution might be using parametrized modules, but I was also >> thinking >>> to add some specialized field in ewgi environment to pass data to >>> applications. >> The opaque data is required because ErlyWeb (and sometimes application >> code) uses it to store arbitrary app metadata. I don't see a way >> around it. >> >> It seems like there are two separate issues here -- configuration >> for erlyweb which is bubbled up from the server, and opaque data >> that is used by erlyweb or an application written in erlyweb. > >> >> yaws_arg:appmoddata() currently stores the former, yaws_arg:opaque() >> stores the latter. >> >> erlyweb should own the opaque functionality, i think the only thing >> missing right now is the ability for ewgi to send erlyweb >> configuration. >> >> the only problem i'm having is that this isn't exactly *only* >> relying on ewgi -- I'm writing an interface for yaws, yaws+ewgi , >> and it'd also need mochiweb + ewgi. I kind of coded myself into a >> knot. The code that Fillipo suggested has the same problem -- there >> needs to be a special interface for both mochiweb and yaws in order >> for erlyweb to use the generic ewgi interface :-/ > > I think we need 3 APIs: HTTP request handling, application > configuration, and application deployment. ewgi, as it stands right > now, only provides the first one. I think its obvious that we want > these kinds of generic APIs outside of erlyweb proper. Do they belong > in ewgi? >
ewgi in my idea is only a tiny interface *definition* on top of the http protocol. Application configuration and application deployment are be application specific :-) so IMHO they don't belong in ewgi. Strictly speaking even the ewgi_yaws and ewgi_mochiweb miodules don't belong to ewgi. They are there because I need to test the interface :-) and as a reference implementation. cheers, filippo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
