I agree that the problem probably lies in the way the validation process works and it's likely that the comment submition had a validation error and user just wasn't notified. That's fine and I can look at that.
However, I still strongly believe in updating the backend if for no other reason then to strip out the rendering component of the CommentServlet. The CommentServlet is redundant to the PageServlet and we don't need it to be doing rendering. My reasoning is because our site is very large and gets quite a bit of traffic, so performance is a big issue for us. If I do some quick math I can see that if we have 2000 blogs each w/ 100 entries then we have 200,000 permalinks. Currently the CommentServlet (redundantly) acts like a permalink on most of the Roller themes, so that means we actually have 400,000 permalinks. That's already a huge bump for no reason, but you also have to remember that the CommentServlet is not cached, so every hit to that servlet triggers a full page rendering. I'm sorry, but that's just not efficient and doesn't make much sense. Unless someone has a good reason why the CommentServlet needs to render pages then I think this is something that needs to be done. -- Allen On Fri, 2005-09-09 at 12:20, Matt Raible wrote: > On 9/9/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > > team, > > > > I have written up a quick proposal on rewriting the current CommentServlet > > mainly to remove the velocity rendering component, but also to tidy things > > up a bit. > > > > http://www.rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_CommentsRewrite > > > > One item that has been a mysterious, but recurring issue for us on > > blogs.sun.com is some problems with posting comments. Fairly regularly > > users complain that their comment posting seemed to work, however the > > comment just didn't show up so they have to post it again and again until > > it works. > > I believe this is largely caused by "twisty" comments and the > MathAuthenticator. If you answer the question wrong, or in any way > navigate away from a page - your comment is gone. The > MathAuthenticator could be causing the issue with other comment UIs as > well - since the fact that authentication failed is often not > displayed prominently. > > Because of these suspicions, I believe a better solution is to fix the > UI rather than the backend. Maybe using Ajax (or just plain ol' > JavaScript) to do the authentication before submitting the form would > help? > > Matt > > > > > I have actually seen this happen to me once and it doesn't throw any > > exceptions or cause any errors so it's pretty tough to track down why it's > > happening. Anyways, the result is that our users are asking for the > > problem to be fixed and since comments are such an integral part of > > blogging that seems pretty reasonable. > > > > Check out the proposal when you get a chance. All thoughts, comments, > > ideas, and changes are welcome. And please make sure to include your vote > > along with any comments. > > > > Cheers. > > > > -- Allen > > > >
