On Thu, 2002-07-11 at 07:41, Kip Hampton wrote: > At 10:30 AM 07/11/2002 -0400, Christopher H. Laco wrote: > >While we're on this topic... > > > >I've had reason in the past to change the QueryString module so you can > >specify the 'name' in the name=value pair. > > > >Something like.. > > > >PerlSetVar AxStyleChooserQueryStringKey mystyle > >[I hate that the var name is this long, but it's clear, any other ideas?] > > No. Unambiguous is better than terse here, I think (its not like its > something that folks would have to type very often, anyway). > > > >So then requests could be made using *.xsp?mystyle=style1 > > > >The reasoning was that [albeit rare], style= was already takin for something > >else. > >The same theory applies to StyleChooser by cookies > > > >Would this be something that could make it into the source (ala submitting a > >patch), or just a 'silly feature'? > > I don't think its silly at all; AxKit should just get out of the way, when > and where it can. I'd be +1 on adding your patch, anyone else have thoughts?
I would agree with that, as long as the default remains what it is today when there is no StringKey specified. I would almost think that these options should have been prefixed with 'axkit-' so that they do not conflict when someone drops them into their application. I have had a similar problem where I have a XSLT style sheet that uses variable that have the same name as parameters being passed in on the URI. You end up with a duplicate variable error from XSLT. I would almost go so far as to say that these parameters passed to XSLT should also be prefixed with axkit- so that they do not get in the way. -- Owen Stenseth --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
