On 10/27/2011 12:22 PM, Richard Alimi wrote:
[...]
To keep the specification simple, perhaps it would be more clear to
state it in the affirmative -- something to the effect of "the ALTO
Server need only include source/destination pairs that exist" (and we
can ensure that the existing rules are in line with this). Then ALTO
Clients can just iterate through the returned JSON and fill in the
entries in the matrix that they find (and just not complain about
missing ones). The actual syntax of the JSON matters less then -
servers could either omit the entire row for the source PID, or have
the row empty, whatever.
Any complaints with that?
Rich: Works for me.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
