[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public review comment: extensibility of URLs
For 2.0 we extended our WSRP extensions and added the ability to describe these. Ongoing with this, we anticipated that future proposals can be brought in early/easy before finessing 3.0 based on WSRP 2.0 extensions. My impression is that having "just" the WSRP 2.0 protocol payload extensions is not sufficient to solve/fully support future proposals. One main missing part might be the extensibility of our WSRP URLs (and symmetrically templates). Our BNF is pretty fixed and not extensible. This might prevent furure proposals to work because an extension's behavior can not be triggered via URL invocation. Therefor I would propose to extend our URLs in two ways: 1. extend the BNF to allow other URL types 2. extend BNF to allow custom URL parameters What needs discussion if we decide to accept the proposal is to decide how Consumer's will handle URL types they don't know and if/how Consumers propagate unknown URL parameters. Mit freundlichen Gruessen / best regards, Richard Jacob ______________________________________________________ IBM Lab Boeblingen, Germany Dept.8288, WebSphere Portal Server Development WSRP Technical Lead WSRP Standardization Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 Email: mailto:richard.jacob@de.ibm.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]