> > The web site still uses 3.1.6, which I think doesn't support
> > compression.
>
> Not for the word database, but it does support compression for the
> excerpts in db.docdb.  I thought it was on by default, but it appears
> I was mistaken.  So, no, I don't believe we have compression enabled,
> but I don't know how much space we'd save by doing so.

  The old buggy compressor is about an 8-1 compression margin.  Using
3.2.0 we are only about 3-1, but gzip based is so far much less buggy.

  So how about we move to 3.2.0 on our webserver?

> To answer Neal's question first, though, you point ssh to shell.sf.net,
> and login using your SF.net user name and password.

  Thanks.

  Looks like our project is here once you get in:

  /home/groups/h/ht/htdig/

Thanks!

FYI: I committed the libhtdigphp code last week.


Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to