0.4.0 to 0.4.2 (August00)

  Fixed a couple of problems that appear when FSSession is run on windows
  platforms. Under Win os.rename raises an exception if file already exists.
  Also made the code more robust in case one calls FSSession twice.

  FSSession has been checked against the situation where many concurrent
  users access the same SessionUID. No errors are raised but sometimes
  updates were lost as it was expected. In any case each user is supposed to
  have his own unique id.

0.3.1 to 0.4.0 (June00)

  Fixed a bug in the transaction management. Now tpc_finish, contains
  code that wil certainly succed and all pickling and writing is done
  at tpc_begin time. (IMO TM.py should be made more clear. _begin is
  called at registration time which is a bit confusing. Initially I
  though _begin was called by tpc_begin)


0.3.0 to 0.3.1 (Apr00)

  Fixed:

  - Jens Quade reported a bug in method 'url'

  - Dr. Peer Griebel reported a bug with cookie date format under
  different locales and subsequently suggested rfc1123_date() in
  OFS/Image.py.

  - Stores SessionUID in a cookie if it has changed.


0.2.4 to 0.3.0 (Mar00)

  - Fixed the __init__ method of FSSession. 

0.2.3 to 0.2.4 (Mar00)

  - After discussing the (TransactionManager) TM problem with Hung
  Jung Lu, I decided to move the TM related code inside object Store
  and make it non Persistent. I still believe that DC should decouple
  TM from ZODB completely. I am suprised they did not designed it as
  such from the begining. Now all Transaction related calls are
  captured in the non persistent Store which is responsible in turn to
  notify the FSSession object.


0.2.1 to 0.2.3 (Feb00)

  - Playing with CVS :-)

0.2.0 to 0.2.1 (Feb00)

  - dump/load now use cPickle

  - Method getName returns the SessionUID (for SQLSession
    compatibility)

  - __call__ now takes an optional argument noCookie, which if set
    disables cookie setting for current session.

0.1.0 to 0.2.0 (Dec99)

  Major rewrite. FSSession is now a product and participates in Zope's
  transaction machinery. 

  - New method url introduced which takes a URL as an argument and
    returns the URL with Session info added, depending whether the
    client has cookies enabled or not.

  - New SessionUID are not created for each request. Old ones are
    reused unless the _force_new_session is set in the REQUEST object.

  - session data are stored in memory and only commited to disk at the
    end of the tranaction. This should improve performance
    considerably over version 0.1.0

  - _force_new_session flag introduced to comply with SQLSession. If
    set then a new session is forced.
