[fpc-pascal] Re: URIParser
michael.vancanneyt at wisa.be
michael.vancanneyt at wisa.be
Wed May 18 16:56:01 CEST 2011
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 at 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.
More information about the fpc-pascal
mailing list