Re: tech aspects: how xaraya gets rid of ?& w/o mod_rw?

"mulpinBR - 111.898.068 > http://br.xaraya.com" <xaraya-ZJ5JVcqp1wkXtBFVwdE/[email protected]>
Newsgroups gmane.comp.cms.xaraya.curiosa
Organization Xaraya News Server
Message-ID <[email protected]>
Thanks for your patience and attention, mike!

X's,
Murilo

"mikespub" <[email protected]> escreveu na mensagem
news:[email protected]
| In article <bo8c26$t87$1-111RdWWlOxkOkXtL6OYfHgC/[email protected]>, "mulpinBR - 111.898.068
> http://br.xaraya.com" <xaraya-ZJ5JVcqp1wkXtBFVwdE/[email protected]> wrote:
| >As you might know, I'm not exatcly a programmer, not even a good
| >code-hacker. And didn't look at any piece of code from xaraya yet.
But
| >I'm trying to convince our programmer that it's possible to get rid
of
| >?& in urls w/o using mod_rw.
| >
| >Which functions handle this? Is there any other trick? Is it
| >multi-OS/server?
| >
| >Thanks in advance,
| >Murilo
| >
| Did you have a look at RFC 23 yet ?
|
| The main "trick" with index.php/more/stuff/here is that web servers
| support additional path information *after* the script itself
(index.php
| here), and they put that in PATH_INFO. That's been around since
| the early days of CGI programs/scripts, and has been supported
| for related technologies like PHP or ASP afterwards as well.
|
| The rest is a matter of letting Xaraya know how to encode and
| decode those URLs, and that's where the <module>_userapi_encode_
| shorturl() and <module>_userapi_decode_shorturl() functions come in.
|
| See http://docs.xaraya.com/docs/rfcs/rfc0023.html for details...
|
| Mike.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.