Hi,
this is a patch that implements what was discussed in this thread:
http://sourceforge.net/forum/forum.php?thread_id=1010217&forum_id=248759
I modified html.pm and bayes.pm
In html.pm, I modified url_handler__ which now has a handler for /reclassify_to_bucket. From there,
history_reclassify is called, which got slightly modified.
In bayes.pm, I added a global (to that module) configuration variable. The state of this variable then
decides in classify_and_modify whether a X-POPFile-Reclassify-As-bucket header is added or not.
Manni
Logged In: YES
user_id=565464
After playing around with this for a while, I had to notice that my email client is severly limited in its
hyperlink handling capabilities. This has sometimes led to links that didn't correspond to what was in the
header. And because the information about the new bucket comes last in the URL, the bucket
information often was the one to suffer most.
Anyway, I noticed that POPFile or Bayes.pm to be more exact, never checks whether it is about to
reclassify to an existing bucket. It will happily do the reclassification to anything that has a name. I
could modify the patch to check for a valid bucket. OR Bayes.pm could be updated accordingly. I guess
other modules would otherwise have to do the same kind of sanity checking (xmlrpc.pm for instance).
Manni