Comments on: Problems With Vodka http://jsedlak.org/2008/12/01/problems-with-vodka/ Fri, 09 Jul 2010 23:43:27 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: John Sedlak http://jsedlak.org/2008/12/01/problems-with-vodka/comment-page-1/#comment-868 John Sedlak Wed, 03 Dec 2008 01:35:12 +0000 http://jsedlak.com/?p=145#comment-868 Well Vodka is not a CMS in the common sense of the terminology. I am not supplying any client side software initially because that isn't the goal of my senior project. Rather Vodka is just the services that a client would connect to and consume. The problem I have run into is that because I know the clients will want the content in HTML form, I have built in translation functionality. My solution to this will to support external template factories. If the client has their own local (or remote) templating provider, they have always been welcome to use that. They can grab the XML from the content and just go with that. Well Vodka is not a CMS in the common sense of the terminology. I am not supplying any client side software initially because that isn’t the goal of my senior project.

Rather Vodka is just the services that a client would connect to and consume. The problem I have run into is that because I know the clients will want the content in HTML form, I have built in translation functionality.

My solution to this will to support external template factories. If the client has their own local (or remote) templating provider, they have always been welcome to use that. They can grab the XML from the content and just go with that.

]]> By: malfunct http://jsedlak.org/2008/12/01/problems-with-vodka/comment-page-1/#comment-867 malfunct Mon, 01 Dec 2008 18:43:36 +0000 http://jsedlak.com/?p=145#comment-867 Sounds like you want it to be ajaxy. Have a standard template html and .js file that downloads the two pieces of content (xsl and xml) and transforms them then displays them. Make your server content such that no item changes and there is no expiration date and you can save a lot of traffic with caching even though your content is dynamic as the template, the xsl, the .js and probably a .css only has to be sent once. Sounds like you want it to be ajaxy. Have a standard template html and .js file that downloads the two pieces of content (xsl and xml) and transforms them then displays them. Make your server content such that no item changes and there is no expiration date and you can save a lot of traffic with caching even though your content is dynamic as the template, the xsl, the .js and probably a .css only has to be sent once.

]]>