Kees Jongenburger <[EMAIL PROTECTED]> wrote: > >>> - SCAN, including the org.mmbase.module.gui.html.* classes and > >>> supporting util classes (i.e. scanpage) > >>> This includes removing SCAN specific hooks from some core classes > >>> > >> note that we have to be backwards compatible. I am willing to help with > >> creating a SCAN application with all the scan related stuff. > > > >The main problem are the SCAN hooks in MMObjectBuilder (preCommit and > >such). These should either be made generic (not dependent on the > >scanpage object and such), or another solution should be found. > > Still scanpage is about the best thing remaining from scan. we currently > send requests and responses directely into the core witch is IMHO a very > bad practice
Scanpage is a wrapper for request en response objects, isn't it? It looks a bit like JSP's PageContext object. Using one object to wrap those kind of things might be a good idea, because it will be easier to add yet another field or some functionality, but essentially I don't think it is very essential, or suddenly very bad practice to pass the more or less generic Request and Response interfaces in stead. The bad thing of scanpage is it's silly name and bloated implementation, and just for that I would already not accept it. While a better alternative is lacking, e.g. in taglib, I'd prefer somehow passing the request and response objects themselves e.g. into functions. Michiel -- Michiel Meeuwissen Mediacentrum 140 H'sum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
