cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Knodt <torstenkn...@datas-world.de>
Subject cocoon:// design bug?
Date Fri, 16 May 2003 20:42:39 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,
as some perhaps read, I'm currently working on maintaining the URI's during 
traversal through the pipelines. Now I found something strange. For accessing 
the root sitemap, the cocoon protocol uses cocoon://. The problem is, that 
this marks the part after this, before the next / as a hostname, and e.g. 
java.net.URI can't relativize this pathes.
What are your opinions?
Would you agree to change this?
And do you have ideas?

My ideas so far:
The problem is, that you can't give a protocol and a relative URI. My idea 
would be to help to get an absolute URI. We use an input module, which gives 
back a prefix to the actual pipeline. The cocoon protocol will be handled 
like the file protocol. So you can either give an absolute URI, or use a 
relative uri, by prepending the prefix to the current pipeline.
What do you think?

Thanks in advance
	Torsten
- -- 
Domain in provider transition, hope for smoothness. Planed date is 24.7.2003
pub 1024D/4CD29A2C 2001-01-12 Torsten Knodt <torstenknodt@datas-world.de>
 Schl.-Fingerabdruck = A2B1 C626 F819 7C58 B2F9 4F4C BF16 64B6 4CD2 9A2C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+xU0/vxZktkzSmiwRApWfAKCZwnaDErVJ+fat8CnyQraFju6CMgCeLlLx
ISNFazGZkdb/BEVxLbLDDKk=
=gG0O
-----END PGP SIGNATURE-----


Mime
View raw message