I've got three recent projects built with web.py - all of them API services.
My first project with web.py was a game analytics API server. It was pretty functional, but it took some time to get it to deploy properly. The first deployment lit web.py up as an nginx uwsgi application, but this appeared to fork for every request. This played merry hell with the in application connection pooling I was doing with psycopg2.pool. It took some time to figure out exactly what was going wrong, but once we did we redeployed with 80->8080 port forwarding to the built in web server, which I don't think was a particularly optimal solution. Still, it was able to handle the data stream pretty well. Better documentation about deployment options and some of the implications there would be pretty smashing. Also, a better built in web server. The second project was a log merging application for the QA department. It allowed them to do some basic analytics testing and make sure that things went as they were supposed to with the above project. It also ran via port forwarding and the native web server. The company downsized from 50ish to the C levels shortly after this was finished, but the QA team thought it was the best thing since sliced bread. The third project is an IAP verification service that I wrote is an IAP verification service (https://github.com/wizzat/iapservice) that is intended to be deployed via port forwarding and the built in web server. To the best of my knowledge the IAP service isn't in production anywhere, even at the company I was working with while between jobs. I haven't really been able to maintain it or expand it because my time has been gobbled up by a massive 4 hour commute at my new job. I'm in the process of writing a new API service right now, but the stubbed out web framework is written with Tornado. I wanted to broaden my horizons a bit, and the new asynchronous task stuff looked super snazzy. -Mark On Sunday, October 27, 2013 3:12:34 PM UTC-7, Anand wrote: > > Hi, > > I would like to know who is using web.py, what they like about it and what > features they wish to have. If you are using web.py for any of your > projects, please let me know. > > Let me start with myself. > > I use web.py for openlibrary.org. Its been running from quite some time > and I usually don't add ton of new features except some minor changes once > in a while. > > My wishlist: > > It is quite some time since I've built any new applications using web.py, > but wish web.py had the following: > > * nice documentation. it would be nice to have sphinx documentation for > web.py > * a way to write web.py extensions so that it is easier to use third-party > libraries along with web.py > > What about you? > > Anand > > -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy. For more options, visit https://groups.google.com/groups/opt_out.
