On Feb 11, 2008, at 12:17 PM, Dmitrii 'Mamut' Dimandt wrote:
> David King wrote:
>>
>>> That is, instead of explicitly passing the {ewr, Component, Method,
>>> Params} we could do something like {ewr, Component, Method, {magic,
>>> Params}} and redirect the user to http://site/Component/Method while
>>> preserving all the Params...
>>>
>> You could do this pretty easily with a not-so-fancy fancy session
>> manager process. Since you're actually specifying the Params that you
>> want to pass and only preserving those, you don't even need
>> continuations to do it (unless you're hoping to resume inline, which
>> it doesn't look like you are).
>>
>> If you are hoping to resume inline, you could simulate it with
>> something like:
>>
>> %% prepare the continuation
>> session_manager:new(Params,fun(MoreParams) ->
>> %% additional processing....
>> {ewc, controller, function2, [results_of(Params,MoreParams)]
>> end
>> end),
>>
>> %% and return the intermediate result
>> {ewc, controller,function,[foo]}.
>>
>>
> This would still require a fancy session manager that could figure
> out which request exactly to serve and how to clean up unused
> requests...
I have limited experience with continuation-based web frameworks, but
the one I'm familiar with, SISCweb, has the same issue when it comes
to expiring stale continuations. Having a configurable staleness
interval and a reaper process to kill the stale "continuations" seems
like the easiest way to go.
--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
-~----------~----~----~----~------~----~------~--~---
