Re: Thoughts on comments package
Wari Wahab <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <1076663082.6589.23.camel@minisync> |
On Fri, 2004-02-13 at 16:19, Ted Leung wrote: > It seems like a waste for a trackback handler to run all the way > through the pyblosxom pipeline in order to report a failure. Yes, trackback handler is it's own CGI script, but I was talking about other plugins that can get the renderer from the args it receives as the renderer is in the request object. > Actually, thanks for the reminder. I came to web programming late and > went directly to Java, so I tend to not think of things that are second > nature to people that have had to wrestle with CGI scripts. I guess I > can try to do the hidden field thing. I can make the comment renderer > look for those fields and fake an entry for preview. But it's nasty > ugly. Hehe.. I know what you mean... :-P > Don't worry - I'm not advocating building a session mechanism. But I do > think that trying to combine everything into one mega handler (as was > being proposed) is going to have some interesting challenges if we want to try > and handle everything that we can do now. I can see the headlines *Pyblosxom replaces Zope* and *Pyblosxom, your all in one CMS that can plug into your CRM and ERP software.* Just what is everything? * Data representation? * Data management? When I see that people used pyblosxom as some kind of database for documents and other wierd stuff (that bonzai -> pyblosxom integration counts as the wierdest), I'm not sure what pyblosxom is anymore :) ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click