Single User vs Multi User quetions

[Chris Muller]

Ah, yes, I was a bit loose with the "session" vs. "user" nomenclature.
 This matters in the context of a web-server app, sorry!

I was equally loose in my other comment:

>> Changes by other users are not visible to a session until it crosses a
>
>> transaction boundary with #begin, #commit or #abort.

which should more precisely be stated as,

"Changes by other *sessions* are not visible to a session until it
crosses a transaction boundary with #begin, #commit or #abort."

Regards,
  Chris


On Tue, Jan 20, 2009 at 12:26 AM, Milan Zimmermann
<milan.zimmermann at sympatico.ca> wrote:
> Hi Chris,
>
> Thanks for your comments - my notes inline:
>
> On Monday 19 January 2009, Chris Muller wrote:
>
>> Hi,
>
>>
>
>> > Continuing with the examples in
>
>> >
>
>> > http://wiki.squeak.org/squeak/2689
>
>> >
>
>> > It sounds like when I want to have more than 1 connection (session) to
>
>> > Magma, I have to use the "Server/Client" connection mode described there
>
>> > - the single user mode would not allow 2 correctly functional sessions,
>
>> > is that correct?
>
>>
>
>> No, you may have many locally-connected sessions. Which part of the
>
>> documentation "sounds like" otherwise?
>
> Well, I misread. I realize "single user" is not equivalent to "single
> session", this is what I misread:
>
> "Single-user mode
>
> If you know will be operating in a single-user environment, starting a
> second image to run the server may not always be convenient."
>
> I inferred that multi user requires client/server environment, (which can
> run in single or multiple images - I hope I understand correctly that this
> is true), but I erroneously assumed
>
> "single user" = "single session."
>
>>
>
>> > Also a follow up question: I am not sure how to understand the
>> > following:
>
>> >
>
>> > "While your session is connected, it is recommended you keep up-to-date
>
>> > every 30 seconds or so changes made by other users will be reflected in
>
>> > the objects you visit."
>
>>
>
>> Changes by other users are not visible to a session until it crosses a
>
>> transaction boundary with #begin, #commit or #abort.
>
> ok, that is clear,
>
> Thanks, Milan
>
>>
>
>> - Chris
>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>
>