so, if this is a class, would Session be an appropriate superclass for a WebSession class? or any other type of Session class? That particular name would seem to collide with other forms of Sessions, wouldn't it? Or is this safely hidden in a Pharo Environment, so it won't collide elsewhere (or entice other developers to try to use it for other Session style objects)?
On Fri, Sep 13, 2013 at 12:15 AM, Stéphane Ducasse < stephane.duca...@inria.fr> wrote: > so could you do another iteration on it. > > Stef > > On Sep 13, 2013, at 1:51 AM, Igor Stasenko <siguc...@gmail.com> wrote: > > Even more, it feels like we introducing another global (so users can write > 'Session current' , but why not just 'Session' then?) and so a step > backwards as to me. > Because we trying to get rid of all those Display, World, InputSensor , > ActiveHande etc globals for years. > > And last thing: there should be only one way to get current session > object. now there's two: > Smalltalk session > and > Session current > > and so, users now will inevitably raise the question: what is the right > 'true' API for accessing it? > and inevitably we will have two fighting camps, if we leave this thing in > image and be used in various projects. > > > > > On 13 September 2013 01:33, Igor Stasenko <siguc...@gmail.com> wrote: > >> +1 too. >> Session is a bad name for a class. >> More than that, the people who introduced it, >> didn't care about: >> - removing unused session ivar from SmalltalkImage class >> - that putting #reset in Session class side, means exposing resetting >> mechanism to >> public, instead of keeping it private (and it is quite important to keep >> it private, >> because session should be reset once and only once and only in single , >> fully controllable place) >> >> from that perspective, i'd prefer using 'session' ivar in SmalltalkImage >> instead of >> 'current' in Session. >> >> >> >> >> On 12 September 2013 15:13, Esteban A. Maringolo <emaring...@gmail.com>wrote: >> >>> +1 >>> >>> Very abstract names are fine when you have namespaces, otherwise I >>> rather chose more specific names. >>> >>> Regards! >>> >>> Esteban A. Maringolo >>> >>> >>> 2013/9/12 Torsten Bergmann <asta...@gmx.de> >>> >>>> In Pharo 3.0 there is a new class "Session" - to represent the current >>>> smalltalk >>>> session. Using the term "Session" is very abstract. >>>> >>>> IMHO I would rather like to see it named more specific like >>>> "ImageSession", >>>> "PharoSession" or "SmalltalkSession" before it get used too much. >>>> >>>> Any comments? >>>> T. >>>> >>>> >>>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Best regards, > Igor Stasenko. > > >
