TweetDeck (http://www.tweetdeck.com) is hiring for a backend software
engineer position in London, UK. We'd also be willing to consider
applicants located in New York, NY, USA, to work out of our New York
office at Betaworks (http://www.betaworks.com).
At TweetDeck we're trying to build the best t
Hey!
On a somewhat related note: are you people already using Twisted? Have
your experiences been positive? We're always looking for Success
Stories (http://twistedmatrix.com/trac/wiki/SuccessStories) :-)
thanks in advance
Laurens
___
Twisted-Python m
On Mon, Jun 7, 2010 at 12:25 PM, Laurens Van Houtven wrote:
> Hey!
>
>
> On a somewhat related note: are you people already using Twisted? Have
> your experiences been positive? We're always looking for Success
> Stories (http://twistedmatrix.com/trac/wiki/SuccessStories) :-)
Hi Laurens,
You'll
On Sun, 2010-06-06 at 23:07 -0400, Itamar Turner-Trauring wrote:
> So, sounds like you want to define:
> A) A way to hook up ZeroMQ event loop with Twisted event loop so that
> both ZeroMQ and Twisted code can co-exist in same thread.
JP's proposal is superior to this... but may require changes t
Indeed, from technical perspective I think this is the only sane way
forward.
--
Konrads Smelkovs
Applied IT sorcery.
On Mon, Jun 7, 2010 at 3:27 PM, Itamar Turner-Trauring
wrote:
> On Sun, 2010-06-06 at 23:07 -0400, Itamar Turner-Trauring wrote:
>
> > So, sounds like you want to define:
> > A)
On Jun 6, 2010, at 4:18 PM, Christopher Armstrong wrote:
> We don't want to have any more transport-specific methods on the
> reactor, and this has nothing to do with ZMQ. We also don't want to
> have connectSOCKS, or listenSerialPort. Fortunately, the endpoints
> API[1] was very recently merged t
With regards to the shortcomings of select: there's also a poll-like,
but I have no idea if that improves matters :)
Anyway, I'll tell the ZMQ folks that people are blocking on their
fancy new API that helps with integrating with other event loops.
Thankfully, they were already aware of this techn
On Mon, Jun 7, 2010 at 12:38 PM, Glyph Lefkowitz
wrote:
> While the endpoints APIs are great and everyone should use them, I think
> it's putting it a bit strongly to say that listenTCP and friends will be
> deprecated. Reactors are still pluggable, and we'll need a mechanism for
> endpoints and
On Jun 7, 2010, at 6:07 PM, Christopher Armstrong wrote:
> But will that "lower-level than endpoints" API need to be TCP-specific?
>
> We don't have a listenSerialPort, so why do we need listenTCP (by the way, we
> should totally have a SerialPortEndpoint)?
We totally *should* have a SerialPor
On Jun 6, 2010, at 4:18 PM, Christopher Armstrong wrote:
> ... We also don't want to have connectSOCKS ...
Since I basically said that we *did* possibly want listenSerialPort as an
alternative to the half-working platform-detection stuff that
twisted.internet.serialport does, I do want to draw
On Jun 7, 2010, at 7:30 AM, Reza Lotun wrote:
> Hi Laurens,
>
> You'll notice we're already listed on the Sucess Stories page ;-)
>
> Reza
Reza showed up with a success story before it was cool! He's got good Twisted
indie cred. ;-)
___
Twisted-
11 matches
Mail list logo
