Moving from PHP to C saved my web startup.

Re:Moving from PHP to C saved my web startup. by poink on Friday October 22, 2010 @02:12PM (#1820754)

The more generalized takeaway from this is that you shouldn't use a heavyweight listener to handle polling (or websockets in the near future) if you can avoid it.

PHP was the culprit here, but I can't help but think you'd have had the same problem if you were trying to do the same thing with RoR, any Java app server, or any of the Python frameworks.

Likewise, node.js or Twisted probably would have been an equally effective replacement.

[ Parent | on HN ]

Re:Moving from PHP to C saved my web startup. by rarestblog on Friday October 22, 2010 @02:58PM (#1820975)

I'd probably go with node.js for this task - more manageable. Twisted has a huge learning curve.

[ Parent | on HN ]

Re:Moving from PHP to C saved my web startup. by jemfinch on Friday October 22, 2010 @03:42PM (#1821163)

If you want to stick with Python, tornado is a really good async server without all the learning curve of Twisted.

[ Parent | on HN ]

Re:Moving from PHP to C saved my web startup. by rarestblog on Saturday October 23, 2010 @05:18AM (#1823057)

I wrote my own async servers and having done that (and used Tornado), I'm back on threads :) Async is kind of cool in some cases (long polling for one), but for most cases it's pain.

Right now mostly working on CherryPy's WSGI server.

[ Parent | on HN ]