Thread Specific Storage

  Allows for creation of thread specific
  storage (tss) on a per object basis

  usage::

    YourClassMethod:
	self.tss =TSS()
	self.tss.set(foo)
	self.tss.get(foo)

    other than tss creation, there 
  shouldn't be any need to worry about
  persistent changes (ie notifying persistence
  mechanisms of changes). hadn't thought
  about what happens when you store persistent
  objects here, probably not a good idea.

    This is a python library not a product.

  Why

    this is part of on going project to
    rewrite some of zope's rdbms integration.
    tss is specifically geared towards creation
    of da's which would make equivalent 
    functionality out of zope da level2 and 3.

    it might have utility outside of this
    and therefore is being distributed separate.

  Why do i want to use it?

    you probably don't zope general programming
    model is zodb connection specific anyways, ie each
    thread get its own connection to the zodb and
    hence its own object space, which greatly simplifies
    multithreaded programming. if however you want
    to create persistent in memory objects that aren't
    tied to 

  Resources

    This is implementation mirrors a variant
    of the tss pattern found in POSA II:
    Patterns of Networked and Concurrent Objects
    please consult this book, for further information
    about the pattern and other variants.
  
  Comments

    I have no idea if this work use it at your own 
    risk. Probably need to work through if there are any 
    complications from being attached to the ZODB objects
    when they go and out of memory.

  Author

    Kapil Thangavelu <kvthan@wm.edu>:mailto:kvthan@wm.edu

  License
   
    Public Domain 

    I can't concieve of copyrighting something that
    is implemented a few dozen lines of code.    
