Re: [dspam-users] Problem with history (web interface)

In a nutshell, rather than try to paginate by only viewing portions of the
log (which is hopeless), it reads the entire log and creates a hash
structure which identifies the correct current status of each and every
message once the entire log has been processed. Then it displays only the
correct portion of the hash according to the "page" you're on.

The obvious drawback is that more memory and processing time is used, but I
think it's going to have to be, since theoretically the more recent log
entry could be a retrain of the oldest message.

In practice, it add no observable load to my server with ~100 users, but the
increase might become noticeable on a huge installation... dunno :)

-Aaron

On 1/20/06, Kyle Johnson <kjohnson@fixertec.net> wrote:
>
> What changes does this make?
>
> Kyle Johnson
> Fixertec <http://www.fixertec.net/> - Dynamic Computer and Technology
> Solutions
> 410-609-4191
>
>
> Aaron Wolfe wrote:
>
> I have a fixed version of the cgi that I've given to a few people and sent
> to Jon... actually a few months ago. The problem is that the entire logic
> of the "paging" is broken, so its not just a patch but rather a replacement
> of the whole section of code. I'm not sure that my version is the best way
> to do things either, but it does take into account that fact that retrain
> events effecting a particular message are not neccesarily found nearby in
> the log.
> The fix is based on a 3.6 prerelease version, I'd be happy to integrate it
> into the current cgi if anyone is interested.
>
> -Aaron
>
>
> On 1/20/06, Kyle Johnson <kjohnson@fixertec.net> wrote:
> >
> > We hear you :)
> > This has been discussed a lot in #dspam, as well as a few times here on
> > the mailing list.... The WebUI does need a rewrite, however Jon in a busy
> > man, so it's going to fall into our hands to do this (most likely)
> > Until then, it's best to keep up on the training, so you won't have to
> > remember that much, and to open trained links in a new tab (ctrl+click) in
> > firefox, as it saves a lot of time.
> >
> > Kyle Johnson
> > Fixertec <http://www.fixertec.net/> - Dynamic Computer and Technology
> > Solutions
> > 410-609-4191
> >
> >
> > Pierre Girard wrote:
> >
> > Kyle Johnson wrote:
> >
> > Right now, the problem with the history of the WebUI is that when you
> > click retrain on page > 2, you get sent back to page one. When you go back
> > to page > 2, the message hasn't changed.
> > This is only a visual bug, and the retraining should have still taken
> > place..
> >
> >
> > Yes that's the problem i have. I know it's some sort of visual bug but
> > given the amount of email and spam i receive everyday it's still confusing
> > not to be able to determine if i trained the message or not since i have to
> > rescan the whole thing everytime and often have the same spam more than
> > once. I often end up retraining the same message multiple times.
> >
> >
> >
> >
> >
> >
> >
>
Received on Fri Jan 20 14:54:59 2006