"If the "feed" URI string begins with the string 'feed://' then it
MUST be followed by an authority with optional path and query
string with the scheme for the URI for accessing the data feed
being inferred as the "http" scheme."
So if it starts with feed://, you should change that to http://
before actually retrieving the file, but it could also start with
feed:http://, in which case you should just remove the feed:.
hello scott , all very interesting
i am working on a protocol and since the "mime" types are gone there
is no webconnection possible how can i make an uri
like cuseeme://cuseeme.dyndsn.tv clickable ?
When to do the conversion really depends on what you are doing with
the URIs. If you're only using them to test status, there's no
reason to keep the feed://, but if you're separating the URIs by
type at all, the feed:// might be your only indication that the
file is XML and not HTML or readable text, which is why the scheme
was established.
any links or information are highly appreciated
pace
marc
Peace,
Scott
-- "In a world without walls or fences, who needs Windows and Gates?" http://brain.let.de cuseeme://
cuseeme.dyndns.tv
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
This email sent to email@hidden
