You propose to do compressed transfers over HTTP ignoring the standard support for compressed transfers in HTTP. Programming that with a library doesn't make it "standard".
In Ultraseek, we implemented index synchronization over HTTP with compression. It wasn't that hard. I doubt that compression will make a huge difference, Lucene uses reasonable compression in the indexes already. wunder On 10/29/08 10:35 AM, "Noble Paul നോബിള് नोब्ळ्" <[EMAIL PROTECTED]> wrote: > we are not doing anything non-standard GZipInputStream/GZipOutputStream are > standards. But asking users to setup an extra apache is not fair if we can > manage it with say 5 lines of code On Wed, Oct 29, 2008 at 7:44 PM, Walter > Underwood <[EMAIL PROTECTED]> wrote: > Why invent something when > compression is standard in HTTP? --wunder > > On 10/29/08 4:35 AM, "Noble Paul > നോബിള് नोब्ळ्" <[EMAIL PROTECTED]> > wrote: > >> open a JIRA issue. we > will use a gzip on both ends of the pipe . On > the slave >> side you can > say > <str name="zip">true<str> > as an extra option to compress and >> send > data from server > --Noble > > -- --Noble Paul
