2010/10/26 Andreas Kollegger
> That could be clarified somehow. The "User REST" is providing resources
> that are exposed through the Servlet, so the interaction still happens
> through the servlet. Perhaps new wording and a dotted line. Um... how's
> this...
>
>
> Sure, that'll work
>
>
> On Oc
That could be clarified somehow. The "User REST" is providing resources that
are exposed through the Servlet, so the interaction still happens through the
servlet. Perhaps new wording and a dotted line. Um... how's this...
neo4j deployment #7.pdf
Description: Adobe PDF document
On Oct 26, 20
Good visualization!
One thing: in scenario #7 I'd like the App to access the "User REST"
directly in addition (or instead of) just "REST Servlet". Because that's
what your app would do, go directly through that User REST interface. Would
you agreee?
2010/10/25 Andreas Kollegger
> Great catch, w
Great catch, we should definitely capture that one. Attached...
neo4j deployment #8.pdf
Description: Adobe PDF document
On Oct 25, 2010, at 4:41 PM, Jan Boonen wrote:
> Having read the discussion about an in-memory version of neo4j for unit
> testing last week. I'd propose to add that scenar
Having read the discussion about an in-memory version of neo4j for unit
testing last week. I'd propose to add that scenario as well. As far as I
understood it's almost the same scenario as #1, but I would be triggered
faster to use neo4j when such a scenario was documented.
Cheers,
Jan
On 25-
Hi all,
I've been sketching out various deployment scenarios for Neo4j, and have come
up with the attached list of diagrams. Targeted for this next milestone release
is packaging up scenario #7 into a standalone server install, with a bonus
mechanism for adding extensions to the REST API.
Doe
6 matches
Mail list logo
