__init__.py :  » Network » Twisted » Twisted-1.0.3 » Twisted-1.0.3 » twisted » popsicle » Python Open Source

Home
Python Open Source
1.3.1.2 Python
2.Ajax
3.Aspect Oriented
4.Blog
5.Build
6.Business Application
7.Chart Report
8.Content Management Systems
9.Cryptographic
10.Database
11.Development
12.Editor
13.Email
14.ERP
15.Game 2D 3D
16.GIS
17.GUI
18.IDE
19.Installer
20.IRC
21.Issue Tracker
22.Language Interface
23.Log
24.Math
25.Media Sound Audio
26.Mobile
27.Network
28.Parser
29.PDF
30.Project Management
31.RSS
32.Search
33.Security
34.Template Engines
35.Test
36.UML
37.USB Serial
38.Web Frameworks
39.Web Server
40.Web Services
41.Web Unit
42.Wiki
43.Windows
44.XML
Python Open Source » Network » Twisted 
Twisted » Twisted 1.0.3 » Twisted 1.0.3 » twisted » popsicle » __init__.py
# Twisted, the Framework of Your Internet
# Copyright (C) 2001-2002 Matthew W. Lefkowitz
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of version 2.1 of the GNU Lesser General Public
# License as published by the Free Software Foundation.
#
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
#

"""
Persistent Object Partitioning Strategy Involving Concurrent Lightweight Events

POPSICLE is designed to persist objects as close to transparently as possible.
While complete transparency is impossible with python's semantics, popsicle
strives to preserve three things:

    1. preserve a modicum of referential transparency by using Deferreds for
    all references which can not (or should not!) be immediately resolved

    2. allow for the use of multiple persistence strategies with the same
    object.  Specific back-ends we wish to target: filesystem databases, BSDDB,
    ReiserFS, ZODB, and arbitrary RDBMS schemas.

    3. minimize memory usage by paging unnecessary objects out whenever
    possible, transparently to everything involved.  We want to use Python's
    normal garbage collection mechanisms to accomplish this.


There is a top level persistence manager (the 'freezer') which keeps a weak key
dictionary of {persistent_object: [PersistentReference, [savers]]}

The persistent_object should be 'trained' to expect callable objects that
return Deferreds to populate part of it.  Whenever a persistence mechanism
encounters an ID for a different object that could be loaded...

Each Storage is responsible for its own cache management wrt IDs.

Objects that are dirty should call popsicle.dirty(self) to be added to the
dirty list.  when popsicle.clean() is called, the dirty list will be walked,
notifying all savers for each dirty object.

"""
www.java2java.com | Contact Us
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.