|
|
| Author |
Message |
< Erlyweb mailing list ~ Porting Erlyweb to ewgi (Was:ErlyWeb dependencies and their |
| Guest |
Posted: Fri Jan 04, 2008 11:47 am |
|
|
|
Guest
|
Yariv Sadan wrote:
> On Jan 3, 2008 3:32 AM, Filippo Pacini <filippo.pacini@gmail.com> 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 erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
|
|
|