>>>>> "J" == Jon Stevens <[EMAIL PROTECTED]> writes:
>> (this is to support legacy interfaces, so there's no option of
>> using actions; the page select must be driven by the data
>> requested)
J> Actions can be specified at any time by placing the information
J> into the query string.
I'm not certain I follow. Do you mean I can alter the query string
_after_ receiving the request? This would be very, very useful. Where
can I do this re-writing of the query so subsequent Turbine processing
uses the Action?
I'd understood that the query string, as received from the remote
browser, must contain the action parameter to select the action; the docs
suggest that the action is done before just about everything else and
I hadn't considered that I could deflect it on the fly.
In this particular case, though, I cannot have the browser agents
change their URLs, I must accept the old URLs they are already using,
and those URLs do not include the action parameter -- if I can make my
tests of the form data and then slyly insert the correct Action before
processing continues, this is a much better plan.
J> ... Generally, you can always come up with another solution
J> to chaining two Screen Modules together that ends up being a
J> cleaner design in the long run.
Ok, I'll take your word for it ;)
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
