Yariv Sadan wrote:
> On Jan 3, 2008 3:32 AM, Filippo Pacini <[EMAIL PROTECTED]> wrote:
>> 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.
The ewgi server side is a parametrized module. The parameter is the
"application" (the erlyweb bridge in this case) that handles requests. I
could add a Conf parameter to be stored in the ewgi environment. I'd add
a parameter like:
{ewgi_metadata, [{appl1_name, Conf}, {appl2_name, Conf2}]}
In the code I posted out becomes:
out(Arg) ->
Conf = get_conf_from_yaws(Arg),
Server = ewgi_yaws:new(?MODULE, Conf),
Server:run(Arg).
Might it work? Is it general enough?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
