Thanks Dave. I'll take your suggestions and re-consider how to do it.
newton.dave wrote: > >> It's worth an effort as a web page quite possibly won't work >> properly if its query string is longer than 255 characters. > > It's not that I don't understand the problem, I just don't see it being > much of an issue. > >> JavaScript can achieve it but it's not a good choice because >> clients may diable it. > > They can also type in more than 255 characters no matter how short you > make your parameter names, so it's kind of a losing battle. URL length > restrictions are generally only an issue with pretty old browsers and some > proxies anyway. > >> What do you think? > > If I were dealing with this my first approach would be to re-define the > problem to avoid a GET request in the first place. (Well, my *first* > approach would be to assume that it's rarely, if ever, going to be an > issue.) > > For example, if your goal is to create a savable search link consider > taking POST parameters and massaging them somehow to create a linkable > URL, like TinyURL does. > > If for some reason that was unworkable I'd consider a custom request > processor to perform the request parameter => ActionForm property mapping > if it was required across the entire site, and if it was a single action I > wouldn't do much at all. > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > > -- View this message in context: http://www.nabble.com/Re%3A-Struts-1%3A-how-to-use-different-parameter-names-from-html-field-names-tp21118966p21122465.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
