On 4/25/07, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote:
>2) In CGI, you don't want to package multiple sets of data in a single page >(especially if they are large!). You must >be assuming the typical database backend ! You can still build a CGI script that you use a façade to invoke the correct script. This would allow you to still separate your core files, but use one script which is dependant upon query string to serve the correct page. This would be an option open to you right now.
As autocomplete can potentially use lots of IO, I want to minimize IO . A single cgi file is read in one IO call but with a "façade" you at least make 2 IO calls You asked how you could implement these features w/out modifying the source
code, so I tried to provide some solutions. :)
Thanks. I just want to make sure my needs are taken into account give that autocomplete code is being worked on. It is possible things will be opened up to allow changing the URL
programmatically. It's certainly technically possible, but needing separate URLs for the same field is a corner case.
You can think of one field with a selector control as multiple fields. That is appropriate if the objective is finding info rather than data entry (e.g. the multiple language dictionary example) Thanks and regards Jose -Dan
