Re: RE: ASK confirmation code, wrapped lines etc.

> > With today's CPU speeds, we're talking about nanoseconds to scan an
Email.
>
> I don't agree: I suspect some people are already using ASK on servers,
> which may be already tight on power due to a huge number of messages
> per second processed. Once you gave some performance to users, you can
> never take it back :-)
>
> Moreover, you can imagine some kind of very easy DoS attack, sending
> huge messages to some ASK server...

Sorry, but I must respectfully disagree here. If the confirmation code is
put up at the top of the body of the Email it will not reduce the
performance of a heavily loaded system. ASK doesn't need to scan through the
entire message, just the first couple of lines of the body.

ASK can be set to scan... oh.... say the first 10 lines of the body of the
Email looking for 'conf#'... the amount of time it takes to process that is
totally miniscule. Especially if ASK is changed to truncate everything past
the 10th line. This will actually be a performance IMPROVEMENT because ASK
doesn't truncate as currently configured - thus unnecessarily using up
bandwidth.

Rob Nielson
BYU Football isn't about LIFE and DEATH.
No, it's MUCH more important than that!

Be thankful for problems or idiots would have your job. - Author unknown



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click