On Wed, 18 May 2011, Ludo Brands wrote:
Problem is that the RFC definition for the URI doesn't specify the
individual protocol scheme. So every protocol can specify it's own stuff.
Take the general sip URI:
sip:user:password@host:port;uri-parameters?headers. User can be a telephone
number with folowing definition: global-phone-number = "+"
base-phone-number [isdn-subaddress]
[post-dial] *(area-specifier /
service-provider / future-extension)
Or
local-phone-number = 1*(phonedigit / dtmf-digit /
pause-character) [isdn-subaddress]
[post-dial] area-specifier
*(area-specifier / service-provider /
future-extension)
This definitely will require custom processing.
Also both uri-parameters and headers are name=value pairs. The first are
separated by ";" and the second by "&"...
I'm afraid a universal URI decoder isn't possible.
Great.
In that case I just declare that URIParser will only work for ftp and http
protocols :-)
Michael.
_______________________________________________
fpc-pascal maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
