Bill Roome wrote:
If a server has 1,000 pids, the JSON-encoded full cost map could take
>30 megabytes. 10,000 pids -- ouch! As a result, a server with a
large number of pids may be reluctant to return the full cost map --
or maybe even the full network map.
I see several possible solutions: [...]
There is actually a 5th option --- take a one-time hit for
sending a large map, and subsequent to that, send incremental
updates.
There has been some discussion of incremental updates in
hallway conversations and such; the Quebec City IETF
minutes [1] reflect this.
[1] http://www.ietf.org/proceedings/81/minutes/alto.html#proto
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
