Re: [Pyblosxom-devel] Lucene and comments

[Wari W. <wa...@ho...>]

Theodore W. Leung wrote:

>I'm back and caught up and ready to tackle a few things.
>
>#1.  I'm trying to figure out what is the best way to integrate my Lucene
>code.For the file list, we need to turn the regular
>directory walk into the default behavior (last in the chain) and let each
>plugin before that return a list.  If any plugin in the  chain returns a
>list, then handler processing is done.
>
This was discuss @ 
http://sourceforge.net/mailarchive/forum.php?thread_id=1613664&forum_id=24361 
but still there is no real solution yet. If you've got some ideas, or 
working code, we could try test it out and see if we can use it for all 
situations.

>#2.   For comments I have the following issues
>We need a way to display a single article in a page, (so that we can put the
>comment form up).  This probably just means invoking a different template
>for the single article case.
>
Yup.

>We (again) need a way to handle the comment CGI form post (probably via the
>chain above).
>  
>
Again, the need for your point #1. :) To make life simpler, I'm 
suggesting a comment.cgi type of program to handle comments. We can make 
pyblosxom handle everything, but as feedback mechanism goes, you'll find 
trackback and pingback requiring xmlrpc mechanism to input feedback data.

Then you'll need some management of feedback data, especially deleting 
feedback spam if necessary (of course to know if you're spammed, to need 
to mail every feedbacks to the users).

I'm not sure what Blake have in mind, he would also like pyblosxom to 
handle POST and GET requests too. XMLRPC uses POST too, incompatible 
with GET requests and cgi module won't handle it.

>We need a way to display the comment / trackback / pingback count (retreived
>from the storage api) in story.html (via a variable) -- so every iteration
>through valid_list needs to be able to talk to the storage api.  This seems
>like another place for a callback chain.
>
Counts can be done by the standard load() plugins, iterating thru values 
of entryList at each call by using a standard incremental style of 
iteration. The plugin would call storageAPI to get relevant data of 
comment counts and what nots.

>I just wanted to get your thoughts on this before I plunge ahead.
>  
>
More things to consider, how do you tell pyblosxom that you want to 
disable comments on a particular entry? Would some meta data like:
#comments 0
in an entry work in order to disable comments? Also, what about making 
comments inactive for a particular entry as well? In my other blog I 
have to delete one entry because it recieved 100s of stupid comments and 
I can't disable it in MT (MT will fix that in 2.6)?

Sorry if this mail sounds negative, I'mm all for feedbacks, I want it 
badly, but it does not seem to be an easy task with all these issue 
lying around.