slide and encoding - why?

[Jacob Lund <jl...@qualiware.com>]

Hi all!

I have a question about slide and encoding!

Why would I have to tell the server what encoding to use? Slide stores what
ever is served to it! That is if the url is encoded in UTF8 it will store
that and if it is encoded by escaped local charaterset then it will store
that - I cannot see why slide needs to know!

The only place where is could be interesting is in PUT and PROPPATCH where a
function could be added that could verify that then encoding is UTF8 and not
escaped local charset!

In slide properties there is a sessing called org.apache.slide.urlEncoding!
Will this change the data server to another encoding than the one it was
served?

In the TxXMLFileDescriptorsStore there is a parameter called encoding! Will
this parameter change the encoding of the data when it stores it and then
change it back when it serves back to the slide kernel?

BTW have anyone looked at how webfolders in windows Explorer on Windows XP
works. It will convert national characters to UTF8 and serve that to the
server - this if great! However when it displays what is on the server it
unescapes with local character set! I really do not get that!! In windows
2000 it at least stayed to local charset!!

/Jacob


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

Re: slide and encoding - why?

[Julian Reschke <ju...@gmx.de>]

Jacob Lund wrote:

> BTW have anyone looked at how webfolders in windows Explorer on Windows XP
> works. It will convert national characters to UTF8 and serve that to the
> server - this if great! However when it displays what is on the server it
> unescapes with local character set! I really do not get that!! In windows
> 2000 it at least stayed to local charset!!

In XP, you have to distinguish between the web folder client and the "xp 
webdav mini-redirector". The web folder client should work exactly as on 
Win 2000.

If you have a reproducible issue with one of them, please trace that, 
and post it to this list (or alternatively to the WebDAV mailing list). 
We can then possibly (1) add it to the known-issues list and (2) report 
the bug to Microsoft.

Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

RE: slide and encoding - why?

[Jacob Lund <jl...@qualiware.com>]

There is a setting in slide.properties called org.apache.slide.urlEncoding!
Now I have no idea what it is doing, but maybe this value should be used to
avoid specifying the same thing twice!

The problem with slide and encoding right now is that it will accept both
UTF8 and local encoded URLs! This result in a situation where some users are
uploading files with local encoding and some with UTF8 and they cannot
access each others files - please note that I am talking about the uri and
not the content of the files! This is a big problem!!

In case of UTF8 enabled on the server, all non UFT8 encoded uri's in PUT,
MKCOL and other commands that will create a new uri on the server should be
rejected as incorrect URI! I really believe that this is a must in order to
avoid users with different encodings to corrupt data on a slide server!

/Jacob

-----Original Message-----
From: Oliver Zeigermann [mailto:ozeigermann@c1-fse.de] 
Sent: 21. november 2003 10:02
To: Slide Users Mailing List
Subject: Re: slide and encoding - why?

Jacob Lund wrote:
> In the TxXMLFileDescriptorsStore there is a parameter called encoding!
Will
> this parameter change the encoding of the data when it stores it and then
> change it back when it serves back to the slide kernel?

This should be transparent to the user. It merely gives a hint how to 
store *descriptors*, not content. Using JDOM all valid encodings should 
work, but depending on your character set some may have more overhead 
than others. UTF-8 is a save guess, iso-latin-1/15 would be even better 
for Danish. But, as I said, it does not matter too much. To prevent 
confusion, maybe we should not even specify it in the reference store 
settings as it defaults to UTF-8 any way...

Oliver



---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

Re: slide and encoding - why?

[Oliver Zeigermann <oz...@c1-fse.de>]

Jacob Lund wrote:
> In the TxXMLFileDescriptorsStore there is a parameter called encoding! Will
> this parameter change the encoding of the data when it stores it and then
> change it back when it serves back to the slide kernel?

This should be transparent to the user. It merely gives a hint how to 
store *descriptors*, not content. Using JDOM all valid encodings should 
work, but depending on your character set some may have more overhead 
than others. UTF-8 is a save guess, iso-latin-1/15 would be even better 
for Danish. But, as I said, it does not matter too much. To prevent 
confusion, maybe we should not even specify it in the reference store 
settings as it defaults to UTF-8 any way...

Oliver



---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org