Hi all, I joined the group yesterday.
I've started a small project and in my point of view web2py fits perfectly in this case. The client want: Port a player management to Linux. A player that handles music and database update through FTP downloads, handles the playlist based in programs/schedules sent and stored in database. Management interface to handle some configurations (like FTP servers, schedule updates and others). Handle backups (data and application). And the first feature that made me chose web2py, easy deployment. As the application doesn't have to handle a lot of users, the Rocket server is more than enough to handle threads to communicate with background player, ftp and management interface. I'm very happy to have found a built-in cron on web2py so I can focus in other features instead of build my own scheduler. :-) Also the new scheduler seems useful for the FTP update task. For keep the player working I start a thread (on demand) and it has worked well, I'll send a specific mail to show the idea and get some feedback. So far, I found the documentation in web2py community not so well organized and but this list (and web2py-dev) seem to be very worth, as far as I navigated in the archives. I've been working with Django and before I worked with Plone. I started to play with Python occasionally in 2005 and since 2008 I've been working only with it. :-) I looking forward to help the community. :-) Regards, -- Luciano Pacheco blog.lucmult.com.br
