I like that! Now some beer. Free. Friday.
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Fri, Aug 26, 2011 at 4:22 PM, Rick Bullotta <[email protected]>wrote: > Let's hope that one day soon all of these issues will be "non-issues"! > > Having cool technology always "coming soon" reminds me of this sign: > http://www.rareirishstuff.com/media/13/a20792b12af7736b49978d_m.JPG > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Thomas Fritz > Sent: Friday, August 26, 2011 10:17 AM > To: Neo4j user discussions > Subject: Re: [Neo4j] Websocket Server instead of REST for Neo4J for access > a DB > > Hi. > > Thanks for your fast reply. > > > > > > 2011/8/26 Rick Bullotta <[email protected]>: > > A few potential challenges and reasons to wait on this: > > > > - the Websocket API is still in a state of change > thats true. But i think, since the latest security issues are solved > now with the latest protocol version, hopefully there are no breaking > changes anymore > > > - the existing REST API is synchronous request/response, so there's not a > lot of benefit to switching to websockets without a lot of rework > I think thats a real challenge. Since locking and concurrent writes > come into play - Except you would allow only one websocket connection > > > - The real benefit will be when you Javascript and other web clients can > use a pure binary protocol (not possible today) > I pretty sure it is in the latest protocol definition. But i think no > Browser at this time of writing has implemented the binary parts. > > regards > > Tom > > > > > Rick > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > On Behalf Of Thomas Fritz > > Sent: Friday, August 26, 2011 9:52 AM > > To: Neo4j user discussions > > Subject: [Neo4j] Websocket Server instead of REST for Neo4J for access a > DB > > > > Hi all! > > > > Have anyone thought, or is it possible to implement a Websocket > > Endpoint in Neo4J Server so one can use this instead of the RESTful > > API. Which would be more performant and scalable than the RESTful HTTP > > API. It is possible to use such a Websocket through Java, Node and any > > other Server Side Language and even JavaScript on the client side. > > > > What do you think? > > > > Kind regards > > > > > > > > --- > > Thomas FRITZ > > web http://fritzthomas.com > > twitter http://twitter.com/thomasf > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
