HI Tobias, yes the jdbc driver also uses the transactional http endpoint.
Hmm not sure how well hundreds of labels work out. Perhaps you could outline your domain in a bit more detail so that we can give you some modeling advice on this list? Cheers, Michael On Thu, Aug 7, 2014 at 10:27 AM, Tobias Trelle <[email protected]> wrote: > Hi, > > from what I read from the Wiki etc. there are several transports and APIs > I can choose from when talking to a Neo4j server / embedded instance. Would > this be a good summary: > > > - Native Java API (for embedded mode) > - REST API (using HTTP transport) > - transactional HTTP endpoint (of course, HTTP) > - JDBC driver API > > What transport/protocol is used by the JDBC driver? Is it using the TX > HTTP endpoint? > > A totally different question: when modelling new business domains w/ Neo4j > 2, is it a good choice to have hundreds of node labels to organize sub > graphs within a single database instance? > > TIA, Tobias > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
