PUBLIC MARKS from camel with tags server & xml

The goal for this project is to provide translators to allow for interoperability between applications based on ODF (OpenDocument) 1.0 standards and Microsoft OpenXML based Office applications. As a part of this interoperability initiative, add-ins are being developed that can be installed on top of Microsoft Office Word (document processing), Excel (spreadsheet) and PowerPoint (presentation) applications (Office 2007 / 2003 / XP version) to allow for opening and saving OpenDocument format / ODF files (.odt, .ods and .odp) that adheres to ODF 1.0 specifications. We also provide command line translator utilities that allow doing batch conversions. The converter is based on XSL transformations between two XML formats, along with some pre- and post-processing to manage the packaging (zip / unzip), schema incompatibility processings and the integration into Microsoft Office applications like Word, Excel and PowerPoint. We chose to use an Open Source development model that allows developers from all around the world to participate & contribute to the project. Along with the Add-ins for Microsoft Word (v1.0 released), Excel (under development) and PowerPoint (under development), we also provide a command line translator that allows doing batch conversions. These translators can also be run on the server side for certain scenarios.

Caching is the temporary storage of frequently accessed data in higher speed media (typically SRAM or RAM) for more efficient retrieval. Web caching stores frequently used objects closer to the client through browser, proxy, or server caches. By storing "fresh" objects closer to your users, you avoid round trips to the origin server, reducing bandwidth consumption, server load, and most importantly, latency. This article shows how to configure your Apache server for more efficient caching to save bandwidth and improve performance. Caching is not just for static sites, even dynamic sites can benefit from caching. Graphics and multimedia typically don't change as frequently as (X)HTML files. Graphics that seldom change like logos, headers, and navigation can be given longer expiration times while resources that change more frequently like XHTML and XML files can be given shorter expiration times. By designing your site with caching in mind, you can target different classes of resources to give them different expiration times with only a few lines of code.