Re: File name length on enclosures

I agree.  The feed consumer should be able to dovetail with whatever
filename-shortening mechanism the host OS supports.

--- In [email protected], "Bill Kearney" <wkearney@...> wrote:
>
> This is a bad idea.  The local software should be handling this. 
Best to 
> leave it to the standard offered by the transport used to deliver
it.  Leave 
> it to what http, ftp or the transport's own limits.
> 
> What's next, limits based on OS character set hindrances (or programmer 
> myopia)?  Or, worse yet, ASCII only?  No thanks.
> 
> No software should be handling a URL without some form of
pre-processing 
> anyway (ie for security and/or buffer issues).  So it's trivial for
it to 
> handle re-mapping overly long lengths or unusual characters.  This
has no 
> place in the RSS spec.
> 
> -Bill Kearney
> Sydnic8.com
> 
> ----- Original Message ----- 
> 
> >A possible addition for a future profile.
> >
> > File names should probably not be greater than 31 characters in length
> > for compatibility with OSes that don't allow longer file names (such
> > as Mac OS).
> >
> > Dave
>



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-public/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rss-public/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/