nothing's wrong. The ability to fuck up the system is something normal with the kind of skinnability we have, I'd say. (I'm not really sure what causes the problem - Helma refuses paths longer than 50 elements, but I think we're still far from 50 in this case.)

Anyway, if we really would like to provide nested comments we shouldn't nest the URLs but mount them URL/parent-wise all flat in story/allComments or whatever - this would't interfere with the possibility to display them in a deeply nested way. The only thing we'd have to adapt is also to delete them in story/allComments (or whereever).

i was just wandering what creates this error. doesn't look like exceeding any limit (i didn't know there is a limit of 50 in helma ;-).

it's strange. I have no idea where the error comes from either.

You can see the code if you go here and search for "50". (Isn't the refactored RequestEvaluator cute?) Basically I think of every URL nesting that is deeper than 3 or 4 levels as an application design error, so if we want to allow this kind of behaviour, we should definitely parent comments in a flat space (the only thing that would be affected is replying to them and deleting them). Hm, I guess I'm repeating myself, sorry, I shut up already ;-)

wow, the refactured code really looks much nicer (even i quite understand what's going on there ;-) and yes: mounting comments in a flat space is definetly better than like it's done now (although those nested URLs are pretty useful sometimes, they're getting absurd if someone uses it in an extreme way like the above example).

well, just think about that one intranet server where we already have paths like /antville/code/topics/scheduled+to+read/105/106/110/112/114/116/

+1 definitely for flatten it, and honestly, i think it's a little problematic if you cannot reply to a posting, especially if even hannes cannot explain why... ;->

however, i don't think this is serious. we only messed with the possibilities yesterday, this is not a real life example.

but we are using such a nested comment structure in real life and hence this situation could occur (and it's even worse not to know why and when it does).