Hi Klas,
I would be interested in
On 7/24/07, Emil Eifrem <[EMAIL PROTECTED]> wrote:
> On 7/23/07, Klas Ehnrot <[EMAIL PROTECTED]> wrote:
> > I believe topics like
> >
> > * Wrapping nodes in Java POJOs
> > * Defining a Neo independent API
> > * Creating Managers/Handlers/Factories or what we want to call the managing
> > entity for a particular object representing a stored bean. (where we
> > find finders, create methods etc).
> > * Proper use of transactions.
> > etc
* Trimming NEO for high throughput, logging, intensive reads/writes, caching
* NEO and JPA
* NEO and external storage, URIs and good practices reagarding e.g.
LDAP user data vs. NEO dynamic data
* other wrappers on top of NEO, namely RDF, LDAP, hirarchical (file
systems), security structures (ACLs etc)
* Visualization of network data
* scaling and performance in different aspects (number of nodes,
connections, graph depths)
* multiple clients to one node space or NEO instance (central data storage)
etc etc, maybe I can come up with some more ...
/peter
> >
> > What else do you guys think is needed in a "Design with Neo" guide?
>
> Hmm, well, how to lookup nodes by property values as mentioned in the
> other thread. Also, different node space designs ("star design",
> "circle design", etc) and their tradeoffs. I'm sure there's lots of
> other things but I can't think of any at the moment...
>
> Cheers,
>
> --
> Emil Eifrém, CEO [EMAIL PROTECTED]
> Neo Persistence AB, www.neopersistence.com
> Cell: +46 733 462 271 | US Cell: 206 403 8808
> _______________________________________________
> Neo mailing list
> [email protected]
> http://lists.neo4j.org/mailman/listinfo/user
>
>
_______________________________________________
Neo mailing list
[email protected]
http://lists.neo4j.org/mailman/listinfo/user
