G
gus bjorklund
Guest
a single avm with multiple sessions or an avm per session amount to the same thing. the agent process has one copy of the avm code (actually one copy shared amongst all the agent processes), some agent specific private data, a copy of the session-specific data for each (configurable number) of the sessions, several utility threads, and some different (configurable) number of worker threads that take an incoming request, bind to relevant session's data, perform the request, and send the reply back. each request for a given session may be handled by a different worker thread. worker threads sleep when there is nothing for them to do. each set of session data has lots of stuff that is not shared with other sessions, such as database connections, lbi and dbi and other kinds of files and so on.
Continue reading...
Continue reading...