Hi Brian, Would you expect state to be a per-connection thing, a per-server thing, or what? The former is reasonably possible, but the latter would force all requests to be serialized to a single Erlang process.
-Todd On Wed, Dec 9, 2009 at 11:18 AM, Brian McKinney <[email protected]> wrote: > Currently, the callback for the handler under Erlang is defined as follows; > > handle_function(Function, Args) > > It would be nice to propagate state between calls so I could collect > metrics and pass in config information. There are other ways to do this > like wrapping the handler in a gen_server but it would be very convenient > (and simplify things greatly) if the semantics of handle_function are > changed to: > > handle_function(Function, Args, State) -> > {ok, State} | {reply, Reply, State} > > Cheers, > > Brian McKinney
