On 13 September 2013 17:27, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-09-13, at 12:09, Chris Cunningham <cunningham.cb@gmail.com> wrote:
so, if this is a class, would Session be an appropriate superclass for a WebSession class? or any other type of Session class?
I would say so. It is as generic as the name suggests. The class is lightweight and only contains the time when it was created.
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)?
It is a normal class, thus yes, collision is possible. Again, it can easily serve as a superclass for other session-like objects.
i doubt it can serve as a basis, because it is not abstract. Its implementation collides just from a beginning , if you need to have multiple session(s) of same kind per connection to some service, because it uses singleton pattern. Take seaside, for example, it uses separate session per each connection. -- Best regards, Igor Stasenko.