Re: [Twisted-Python] Twisted receiving buffers swamped?

> >>which POSTs structured data (though urlencoded, not JSON) to the > >>codespeed server. > > > >I see. And codespeed parsest that, stores it in a database and produces > >graphics? > > > >It seems, reporting the results via a WAMP RPC to a backend should be > >quite easy to add in speedcenter.py

Re: [Twisted-Python] Twisted receiving buffers swamped?

On 12:15 pm, tobias.oberst...@tavendo.de wrote: >>which POSTs structured data (though urlencoded, not JSON) to the >>codespeed server. > >I see. And codespeed parsest that, stores it in a database and produces >graphics? > >It seems, reporting the results via a WAMP RPC to a backend should be >

Re: [Twisted-Python] Twisted receiving buffers swamped?

> >> >It seems, reporting the results via a WAMP RPC to a backend should > >> >be quite easy to add in speedcenter.py > >> > >>WAMP? I don't think so. I understand you work in that space a lot > >>but I think you might want to take a step back. The extra complexity > >>of WebSockets is pointless

Re: [Twisted-Python] Twisted receiving buffers swamped?

> On Jan 18, 2015, at 4:46 AM, Tobias Oberstein > wrote: > >>> All the extra complexity is hidden using WAMP and AutobahnJS. >> >> Oh well. I'm not going to spend much more effort to convince you that this >> is >> a bad idea. Maybe someone else will. > > That's ok for me. > I guess we wi