I posted this message after getting more and more familiar with Cocoon, XML, XSL, and XSLT.
WML, PAP, and WAP are also very important technologies, and it is easier to process XML via OpenWave Gateway than to develop WML-ServletOutputStream. Sorry for being 'philosophical' and not pragmatic... Of course, JSON will be the main selling point in nearest future, until someone develops Moogle (~m-Commerce)... Anyway, XML supports wider auditory than custom-made-XML + JSON + Ruby. -----Original Message----- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 4:05 AM To: [email protected] Subject: Re: XML vs. JSON, Python, Ruby Seconded.... I'm happily using the Ruby format with a Rails application. It is very nice that Solr has this flexible output capability. Erik On Nov 22, 2006, at 3:57 AM, Mike Klaas wrote: > On 11/21/06, Fuad Efendi <[EMAIL PROTECTED]> wrote: >> SOLR is a Web-Application with well-defined XML-based API: >> - indexing service >> - asynchronous; no need for 'real time' (content has well-defined >> TTL); can >> use HTTP Caching for increased performance >> - provides native support for XSL >> >> The question: do we really need to maintain JSON/Puby as a >> ServletOutput? We >> can focus on 'Public XML API' only, and provide samples of XSL-to- >> JSON, >> XML-to-WML, and etc... > > -1. Python, ruby, and JSON are going to be increasingly important on > the web, and maintaining those interfaces is a feature that gives solr > a more cutting-edge feel. > > The alternative interfaces can also be much more efficient for > these languages. > > -Mike
