Thanks to all for your help.
My graphs are huge (and contain much more information than the list of
nodes and their edges... I am working with protein-protein interaction
networks) so I have decided to have a persistent object on the server.
I first had to make my objects "pickable" (which was not
[EMAIL PROTECTED] wrote:
Hi,
I'd like to know if I am trying to do something impossible or I am just
being unable to find how to do it. In the latter case, please... help
me...
(snip)
>
My problem is that I don't know how to create a graph_object that
remains persistent through time (it has to be t
[EMAIL PROTECTED] wrote:
My problem is that I don't know how to create a graph_object that
remains persistent through time (it has to be the same graph_object for
One possibility is to have a remote procedure call server that stores
the graph running seperately from your wab application.
Your web
The ZODB (Zope's object database, which can be downloaded and installed
separately from Zope) and Durus (part of the Quixote family, I believe)
are both high quality persistent Python object stores that are used
heavily for web sites.
I've never used the ZODB outside of Zope, and haven't used Duru
Hi,
I'd like to know if I am trying to do something impossible or I am just
being unable to find how to do it. In the latter case, please... help
me...
I´ve implemented a python class Graph, which handles graphs (with its
nodes, edges, finding paths, etc). In my text-menu interface, I can add
nod
