erlang and external authentication -
a simple scenario. user logs in through form baked high level framework (rails let's say) , starts chatting. chat erlang-written , authenticated users can participate in. means, every request (containing session id) comming client side needs verified (authenticated) inside erlang code somehow. erlang knows nothing logged users , needs ask framework information.
the question how design communication between erlang , framework not cause additional bottlenecks?
i thinking storing session ids in erlang well. additional effort related synchronization (when new users log in) , session timeouts causes headache.
there nothing free lunch in case. if keep authentication authority outside erlang have deal headache. can provide caching inside erlang improve speed bottleneck , have deal cache coherency issues. imho best solution make erlang authentication authority , provide authentication high level framework.
Comments
Post a Comment