"Schmidt, Allen J." wrote:
Great! Thanks!
I should be able to give this a try shortly. I use it a lot so that functionality was sorely missed.
Well, the code change was five minutes. But guess how long I waded through code, tried to figure out *which* part of the REQUEST is used to format an URL part, and where and how this occours at all? It took me a whole night, since I have a very limited idea of Zope. The REQUEST variable is a quite ambiguous object - there is the same stuff in different places. Variables occour in the "form" attribute, but the sequence-query doesn't use it - it wants to use the query string directly. If it would use the form attribute, everything would have worked by magic. But things like this will be much faster next time - ly y'rs - chris p.s.: Design question: The QUERY_STRING attribute of the environment is one thing. It is quite near to the (not really relevant) fact that we use a GET in this context. The form attribute is a generalization, since there is always a form attribute, regardless whether we chosed to use a GET or a POST method. The real point is about what part of the REQUEST is used to carry state information. I think there is a missing concept for this: You can see this if you do testing of a Z SQL method. Have a look at the "ext" URL: The URL carries useless information, since the value of the submit button is caried around, which nobody really needs. I'd like to introduce a "state" attribute for REQUEST: This should be the set of attributes intended to be carried around between stateful queries, nothing more and nothing less. Maybe I will submit a proposal to zope-dev. cheers again - chris -- Christian Tismer :^) <mailto:tismer@tismer.com> Mission Impossible 5oftware : Have a break! Take a ride on Python's Kaunstr. 26 : *Starship* http://starship.python.net/ 14163 Berlin : PGP key -> http://wwwkeys.pgp.net/ PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF where do you want to jump today? http://www.stackless.com/