Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devel:xavp [2009/05/27 22:50] miconda |
devel:xavp [2009/07/28 13:09] (current) 82.113.121.84 |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| Proposal and prototype implementation by: | Proposal and prototype implementation by: | ||
| | | ||
| + | |||
| + | CODE IN GIT REPOSITORY BRANCH: daniel/xavp | ||
| + | |||
| </ | </ | ||
| Line 212: | Line 215: | ||
| * **less exposure the name conflicts by grouping** | * **less exposure the name conflicts by grouping** | ||
| * modules can group their internal AVPs under a xavp, so other xavps with same name in global list won't affect the module functionality. Say dispatcher groups its avps under " | * modules can group their internal AVPs under a xavp, so other xavps with same name in global list won't affect the module functionality. Say dispatcher groups its avps under " | ||
| + | |||
| + | * **reduce number of parameters for some modules** | ||
| + | * a module can reserve now only one name for xavp in default list. Inner xavp can have predefined names, without the risk for overlapping with other modules or config | ||
| + | * **dispatcher** module can reserve xavp name " | ||
| ===== Use cases ===== | ===== Use cases ===== | ||
| Line 224: | Line 231: | ||
| * possible in **utils**, to store each line of http response in a grouped xavp list. | * possible in **utils**, to store each line of http response in a grouped xavp list. | ||
| + | ===== Observations ===== | ||
| + | |||
| + | * it is not a replacement to existing AVPs, but an addition, a new class of pseudo-variables | ||
