On Tue, 2010-10-19 at 18:23 -0200, Pedro Padron wrote:
> I will leave the client library as is, and extend it in my application
> to parse the report the way I need. However, I will still need
> different users (for my app), because I will also work with rule
> descriptions in different languages.
Right, moving such parsing (if needed) up in the stack does the trick,
too. My main point was the client's usability with a low barrier and as
little requirements as absolutely needed. If it does not (necessarily)
require any modifications to the server (which includes a need for a
dedicated user), it will be immediately useful to a broader user base.
Regarding language support -- frankly, I haven't checked at all in a
long time and don't care much personally, but I believe the existing
translations to be lagging behind. Putting it mildly.
> Good idea, I'll work on this today =) I'll also add support for
> multiple hosts and zlib compression.
>
> Thanks again for the feedback!
You're welcome.
In particular the size limit is important, since it prevents huge
messages (both ham and spam) from consuming too many resources. SA
itself, as well as spamd, does not have any size constraint and happily
will try no matter what to grab the resources necessary to complete the
scan.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
