is it safe to quit Squeak with an open session

[Chris Muller]

> So if I understand, it is pretty safe for the server?

The existing functionality should be safe for you, but you should test
it with your application.  Actually, if you're going to do that you
could probably more easily implement the generic test case method on
MagmaTestCase.

There is no test case for it but there should be.  I'll try to squeeze
it into r41, or if you crank out a test method for it (i.e., implement
#testSessionReclaimation on MagmaTestCase), it would be a great
addition to r41.  Until a "real" security framework is integrated "to
the core" into Magma, it is prudent to at least close any wide-open
doors to server-oblivion, if we find any.

> the SqueakPlugin
> configuration is only used to review (load) object from the database,
> not commit.

I really need to do a "read-only" session, which can read faster but
not commit.  I think its possible.  Another thing to add to my list..

Regards,
  Chris


On Tue, Mar 4, 2008 at 4:33 AM, Hilaire Fernandes <hilaire at ofset.org> wrote:
> It is my scenario ungraceful termination. But anyway the SqueakPlugin
>  configuration is only used to review (load) object from the database,
>  not commit.
>  So if I understand, it is pretty safe for the server?
>
>
>  Hilaire
>
>
>  Le lundi 03 mars 2008 à 21:18 -0500, Chris Muller a écrit :
>
>
> > If, by "closing Squeak", you mean an ungraceful termination via the
>  > OS-Window exit or termination of the process:
>  >
>  >  - Session resources remain in the server image until enough commits
>  > by other sessions exceeds a threshold whereby the stale session
>  > resources are reclaimed.
>  >  - All uncommitted changes in the image are lost, of course.
>  >  - The image restarts in its previous state.
>
>
> _______________________________________________
>  Magma mailing list
>  Magma at lists.squeakfoundation.org
>  http://lists.squeakfoundation.org/mailman/listinfo/magma
>
>