> Why not change to http://cyclone.io/ and
> https://github.com/fiorix/cyclone

> regards
> joao martins

> Em sexta-feira, 3 de agosto de 2012 07h01min46s UTC-3, Nigel Small
> escreveu:

>> All of which says that removing the dependency is a good idea - I hadn't
>> actually considered the Jython case.

>> If you get a few mins to give the new code a quick try instead, it would
>> be great to hear how it performs.

>> Cheers
>> Nige

>> On 3 August 2012 09:57, Julian Simpson <julian.simpson@neotechnology.**
>> com <julian.simp...@neotechnology.com>> wrote:

>>> On Fri, Aug 3, 2012 at 9:31 AM, Nigel Small <ni...@nigelsmall.net>wrote:

>>>> What problems was Tornado causing you? Similar to the ones I listed?

>>> We were using py2neo under Jython, and there was a transitive dependency
>>> (via Tornado) on a native library.

>>> While there's an open PR for making Tornado work fully under Jython, I
>>> didn't want to wait.

>>> cheers

>>> J.

>>>> On 3 August 2012 09:22, Julian Simpson <julian.simpson@neotechnology.**
>>>> com <julian.simp...@neotechnology.com>> wrote:

>>>>> On Fri, Aug 3, 2012 at 9:18 AM, Lasse Westh-Nielsen <
>>>>> lasse.westh-nielsen@**neopersistence.com<lasse.westh-niel...@neopersistence.com>
>>>>> > wrote:

>>>>>> Nigel,

>>>>>> Good call. We migrated off py2neo for a tiny project we were doing
>>>>>> for exactly this reason (Tornado dependency). I'd been keen to use it again
>>>>>> when we revisit that particular project.

>>>>> +1

>>>>> Removing py2neo from our little project immediately proved py2neo's
>>>>> value: it really hurt to remove it :)

>>>>> J.

>>>>>> Lasse

>>>>>> On Thu, Aug 2, 2012 at 11:10 AM, Nigel Small <ni...@nigelsmall.net>wrote:

>>>>>>> It's fair to say that some people's experience with py2neo 1.2 has
>>>>>>> been a little shaky due to the introduction of Tornado for HTTP messaging.
>>>>>>> This library was chiefly brought in so that asynchronous Cypher queries
>>>>>>> could be executed but has dragged along with it a considerable overhead in
>>>>>>> resource usage, poor support for concurrency and questionable operation
>>>>>>> under Windows.

>>>>>>> For these reasons, I have decided to move away from Tornado for
>>>>>>> py2neo 1.3 and am currently building a simpler, but just as functional HTTP
>>>>>>> layer based on the standard httplib module. This will of course also remove
>>>>>>> the need for a third party dependency when using py2neo in future. In
>>>>>>> addition, I aim to provide full support for concurrent applications since
>>>>>>> this is clearly an area of functionality that many people require.

>>>>>>> If you are willing and able to help with testing for this new
>>>>>>> version, I would be very grateful for the feedback, good or bad! The code
>>>>>>> currently within GitHub contains a *mostly* operational version of
>>>>>>> the new HTTP layer so please let me know if you are able to help and raise
>>>>>>> any issues you find within GitHub.

>>>>>>> Thanks and kind regards
>>>>>>> Nige

>>>>> --
>>>>> *Julian Simpson* *
>>>>> **Software Engineer | Neo Technology*
>>>>> +447967189579 | @builddoctor
>>>>> *As a friend of Neo, register for GraphConnect<http://graphconnect.com/> and
>>>>> get a 20% discount. Code: GCFON*

>>> --
>>> *Julian Simpson* *
>>> **Software Engineer | Neo Technology*
>>> +447967189579 | @builddoctor
>>> *As a friend of Neo, register for GraphConnect<http://graphconnect.com/> and
>>> get a 20% discount. Code: GCFON*