Missing a public way of closing a session about enigma.js HOT 6 CLOSED

Another reason why we might opt into using a default mixin (close() on Doc and Global): Since we may share the session/websocket between apps and global instances, doing .session.close() may break those other instances. Having a mixin that can track instances and close it once it goes down to 0 would solve that.

from enigma.js.

Yes, that's the current (and I think undocumented) way of doing it, it will trigger internal cleanup in enigma.js.

What do you think? I've been thinking about perhaps an app.close() and global.close() mixin, but perhaps closing it on session is good enough.

from enigma.js.

My gut feeling says session.close() is more obvious. If I would see app.close() I would also expect the application to purge from memory server-side

from enigma.js.

True, it could also be another method name though, like app.closeSession(), we'll look into what's better, there might be other things we'd like to expose on .session anyway and in that case it makes more sense to just document the existing method.

from enigma.js.

so I posted the question resolved here on another of @mindspank's questions, but now I have another question that may or may not be germain to this thread. How do I have multiple apps on one session with enigma? is it just a matter of extending the config and calling the qix function again with the updated config or is there some other magic involved?

from enigma.js.

@goldbergjeffrey Hi, see #38 (comment)

from enigma.js.