----- Original Message ----- From: "Brian Olore" <[EMAIL PROTECTED]>
> I understand that the HttpURL class is not integrated with > org.apache.util.URI just yet. Yes, it is... > Do you see any "fairly simple" way for me to > obtain the true URI as it is stored on the filesystem? Unfornately not... because the problem is not just simple... :( > I'd prefer not to stray from the project. You could be one of people to make the project... ;) BTW, the sophisticated way or place to make a URI as an escaped form will be a boundary between the communication and data processing part. Probably, the URI in the communication level is dealt with as byte stream... And the URI in the document level is wanted to deal with and express either of the escaped or not... So actually the boundary would be common-http part, not higher level... I think... It's the same in the server side and client side, I believe... And it makes easier the client to turn on and off the escaped encoding and UTF-8 support for the backward compatiblitiy for the web server... and it could be solved for other problems in the one right place. Then back to the Slide client API problem, it has minor or major bugs with it... For example, like your problem for just now, it unconditionally unescape the URI... Then, is there any way to distinuish escaped or not, or which character encoding was done? No way currently... For a step to solve the problem... for the first time, we should make the boundary... And need to apply other solutions... I think... --^ Sung-Gu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
