Skip to main content

Site now running on django 1.0

hence the bump in minor version - 3.1

While researching on grails and the patterns around it, I looked at django, rails, and lift. All these are quite amazing frameworks that get you started on an application like in 5 mins or less (That includes database layer, view pages, and controllers). Yeah it cannot do everything you want but its there to get you to kick off.

And then I realized, how much effort I am putting in maintaining my site on hand coded - wsgi.webapp based - Python app. So I started working to move this to django based multi app site. If you dont know, I host this site on Google App Engine. It does come with a patched, short featured, django of its own. However, I preferred to use app-engine-patch and deploy with a supplied django 1.0. You get most benefits of django with this port. A very big tip of hat to Waldemar Kornewald and his team for this patch. (Guess what, They also have a similar concept of stitching mutiple js/css files - media generator)

I can see how rapidly I can develop applications and deploy using django. I simply moved jscss.py to django views.py. My first sub-app is a dynamically manageable urls. All the following urls are served by my new django app.

http://sarathonline.com/java
http://sarathonline.com/green

Next, grails?

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>