Hi, this has been discussed before, but without conclusion afaik, so I would like to start this discussion again:
at the moment one can only use the microjax post servlet in an all-or-nothing way. This means that my app needs to decide: I either send POSTs to the microjax servlet and that's all there is. Or I implement POST.esp which means I can do all I wish to do, but I have to replicate all of microjax's servlet functionality (in terms of writing to the repository). I would really like to have a mechanism to mix this, i.e. to extend the microjax servlet with custom logic. And there is actually a real-world use case for it: Spam filtering. Right now I had to revert to a Java servlet to do this (because I did not want to implement POST.esp). IMO it would be great if we had something like "filters" or "pipelines" or whatever you want to call it in microsling. WDYT? Cheers Michael -- Michael Marth, http://dev.day.com
