Monday, April 15, 2002

A current project I'm on will require internationalization. This was not expressed as an upfront requirement, so we've written nothing into the architecture to support this. Runtime label translation is not rocket science, but it would definitely slow everybody down and complicate the testing process. A better solution would be to implement a parallel internationalization effort that would only nominally impact the developers of the application. To accomplish this, my co-architect and I were considering using a custom Apache proxy to sit in front of the back-end web services and rewrite the pages as they go by into the second language. I've done this before on a previous project, where I prototyped Akamai's Edge Side Includes architecture in mod_perl. It worked, was fairly robust, and wasn't too many lines of code. With this architecture in place, we can then add other web applications to the proxy (CRM, HR etc.) and implement a sign domain signon using mod_ldap. I'd say that makes 12 reasons to use apache :-) (see below) 2:55:45 PM      comment []  trackback []

Groove 2.0 press release. "Groove version 2.0 features significant enhancements and new features to both client and server software, including integration with Microsoft Office applications, new project and meeting management toolsets, and, most significantly for large corporate customers, the introduction of customer-hosted management and system integration capabilities."  [Scripting News] Out of the vaporware stage - shoot. Now we have to pay for it. 12:31:39 PM      comment []  trackback []

Apache 2.0 Beats IIS at Its Own Game: Enterprises last week had 11 more reasons to rethink using IIS: 10 new security holes in the Microsoft Web server and the arrival of Apache 2.0. ROTFL! 11:43:50 AM      comment []  trackback []