Server side: ETag VS Cache-Control max-age=xxxx or Expiration VS. I will not cover here the whole topic of the web caching, but there things, which I'dlike to mention.
They are the two caching mechanism: 1) is configured in the server ( in IIS we can set expiration date or expiration timeout ( e.g. max-age ) and on Apache we even can set cache policy for different content types ) 2) no configuration in the server ( client uses "ETags" for cache validation ) - the default one. Now lets consider 1st way, we configure web-server and set expire time as 1 hour ( max-age = 3600 ). What will now happen? Client will download the resource with the header - Cache-Control: max-age = 3600, store this value and will also store the date, when that resource was downloaded. Then every time during 1 hour when client browser receives reference to the resource he will check download date & max-age value of it, and if the content is up-to-date, browser will not send request to the server, and it will use cached resource. Android versus iPhone Development: A Comparison. A few months ago I ventured into the world of Mobile development and created an application (Hudson Helper) for both iPhone and Android.
This article is about my experiences, comparing Android and iPhone development with a focus on tools, platform and the developer experience. Before going much further I should note that my comparison is with considerable bias. I’ve spent the past 12+ years in Java development, having spent much of my career building developer tools. Since January of 2004 I’ve been building plug-ins for Eclipse, and before that plug-ins for NetBeans. This bias is somewhat tempered with several years of C and C++ development. Language, Programming Model and Platform Language. Why can't we be friends? Joomla versus Drupal. I've had more than a few conversations recently about which CMS is better.
From the Joomla camp I hear, "Joomla is easier. Joomla has a great user interface. " From its competitor I hear, "Drupal is more flexible and it has tagging. " It's the Pepsi versus Coke debate for open source CMSes. Okay, that's overstating a bit, but you get the idea. Joomla Thumbs up: Easy deployment More intuitive administration user interface Editing content is simple Lots of polished modules for things like calendars, polls, etc. Thumbs down: 1 installation of the software gives you 1 website Categories can only go two levels deep Limited roles and permission allowances Modules cost you money URLs are not search engine friendly (there is a purchaseable module) Out-of-the-box blogging functionality is mediocre Overall, I find that Joomla is an excellent CMS for basic to complex websites.
The modules were well designed and integrated nicely with the system. Drupal So, which CMS will I take side with?