RE: set user agent with request parameter or path element
-Original Message- From: Jörg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 15. Oktober 2002 12:01 To: [EMAIL PROTECTED] Subject: Re: set user agent with request parameter or path element AFAIK the best then is to use is parameter selector, not the browser selector. But so you want the request parameter? Response time because of selecting on every request? Why don't you use a nested selecting: first parameter, if it's not there use browser selector. But if this is really faster? The idea behind that is that my browser selector list will get really long, and I don't want to duplicate that list in a parameter selector. I want to be able to select the content for the pretended user agent but still set the display xslt according to the real user agent. lg, tom - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: set user agent with request parameter or path element
And why not simply always the browser selector?? Regards, Joerg Thomas Haselberger wrote: -Original Message- From: Jörg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 15. Oktober 2002 12:01 To: [EMAIL PROTECTED] Subject: Re: set user agent with request parameter or path element AFAIK the best then is to use is parameter selector, not the browser selector. But so you want the request parameter? Response time because of selecting on every request? Why don't you use a nested selecting: first parameter, if it's not there use browser selector. But if this is really faster? The idea behind that is that my browser selector list will get really long, and I don't want to duplicate that list in a parameter selector. I want to be able to select the content for the pretended user agent but still set the display xslt according to the real user agent. lg, tom -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de VIRBUS hat jetzt als erster deutscher Softwarehersteller die Zertifizierung für den 3D Secure-Authentifizierungsstandard Verified by Visa erhalten. Details unter http://www.virbus.de/de/press/pressemitteilung/20020828_verified_by_VISA. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: set user agent with request parameter or path element
-Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 15. Oktober 2002 15:17 Subject: Re: set user agent with request parameter or path element And why not simply always the browser selector?? let me explain: a user should be able to select a friends user agent in a list and browse the user agent specific content in order to send one item of this content to the friend. but the wml xslt templates should be used for the *real* user agent of the user. so i have 2 transformations: 1. transform the content according to the real user agent OR the faked user agent to filter the user agent specific content. in both cases i want to match against the browser selector map, that contains eg. browser name=content_one useragent=Nokia/ browser name=content_two useragent=Nokia/ browser name=content_two useragent=Ericsson/ 2. transform it according to the real user agent into wml, matching against different entries in the browser selector map: browser name=nokia_wap useragent=Nokia/ browser name=ericsson_wap useragent=Ericsson/ but how can I supply the browser selector with a different user agent ? thx, tom - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
