Joe, I have rethought recent discussions on multipart requests and have a different proposal. What I would suggest would be to take the whole multipart business out of the framework altogether and to treat it as I think it should be treated, as just another Action.
There is nothing about a multipart request that indicates that it should be take care of in any special manner, especially one that curtails differing solutions unnecessarily, by the framework. There is probably good reason to provide a default solution with an Action in the actions directory and an associated ActionForm so that those who don't quite know how to do these things will have the present solution. This is like providing the DispatchAction, etc. But there is, so far as I know, no good reason to have any solution be part of the web framework itself. That just becomes a stumbling block rather than any help at all. What do you think? I know that no solution has to be part of the framework and this would leave the Action and ActionForm open for whatever solutions, including the default solution. I think we have been "overcoding" this. Any thoughts on this? I cannot think of one reason why the default solution has to be hardwired into the framework. Maybe Martin has some reason that I don't know about. Jack -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
