Re: Persistent Python objects

[Baczek]

On 3 Lut, 20:58, "Tom" <[EMAIL PROTECTED]> wrote:
> What do you suggest for this?

If it needs to be a singleton, you could consider deploying under
FastCGI, I believe the process is started only once and the real
server acts simply as a proxy.

But note that I _believe_, not know :)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Persistent Python objects

[Jeremy Dunck]

On 2/3/07, Tom <[EMAIL PROTECTED]> wrote:
>
> What do you suggest for this?
>

Is there a single shared state among all players, or is it per player?

If the former, you must already have some way of managing concurrency, no?

In any case, it sounds like maybe you want a Twisted.PerspectiveBroker:
http://twistedmatrix.com/projects/core/documentation/howto/pb-intro.html

On the other hand, I'm doing something that's fairly partitioned per
user, and am just using shelve with a backend that manages an MRU
cache.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---