- Oct 27, 2007
- 17,009
- 5
- 0
I'm building some podcast management software and I'm looking to make it "cloud-based" by storing the podcast information on a database and using HTTP GET requests to return the information to the user about new podcasts that are available for download etc. Basically I want all of a user's information to be stored on a web server and use the desktop app as a "thin client" (sorry about the buzz words ).
I figure the best way to do this is to have the app make HTTP GET requests to my server, which will return XML data (the desktop app is already up and running and uses locally stored XML files). So what I need is a simple web service that will query the database and transform the data to XML. I decided to take this opportunity to learn one of the funky dynamic languages that seem to be all the rage at the moment. The application also needs to regularly (maybe once an hour) go through each podcast in the DB and look for new items. This is pretty familiar territory for anyone who has written RSS readers and the like.
So what do you think? Which of these two languages should I learn? Are these appropriate tools for the job I want to do?
I figure the best way to do this is to have the app make HTTP GET requests to my server, which will return XML data (the desktop app is already up and running and uses locally stored XML files). So what I need is a simple web service that will query the database and transform the data to XML. I decided to take this opportunity to learn one of the funky dynamic languages that seem to be all the rage at the moment. The application also needs to regularly (maybe once an hour) go through each podcast in the DB and look for new items. This is pretty familiar territory for anyone who has written RSS readers and the like.
So what do you think? Which of these two languages should I learn? Are these appropriate tools for the job I want to do?