Ben, On Mon, Mar 25, 2013 at 09:43:42PM +0000, Ben Niven-Jenkins wrote: > Sebastian, > > On 25 Mar 2013, at 21:27, Sebastian Kiesel wrote: > > > Wendy, > > > > how would you encode a cost map where most of the entries are > > "I don't know", some are "you should try these" and some are > > "better avoid this PID"? Reducing the number of PIDs so that > > I have only one (or very few) "I don't know"-PIDs is not an > > option because I am planning other cost maps with many details, too. > > What's the driver behind allowing a default cost? Is it to reduce > bytes on the wire or simplify the server (or client) processing in > some way, or something else? > > If the driver is saving bytes on the wire, I don;t think it's worth > it, just either pre-gzip your maps or use Content-Encoding: gzip at > the HTTP layer.
I am thinking about the number of entries in my client-side hashes. Bytes on the wire is another issue. gzip may reduce the size to some 25% or something. Omitting those entries that have the default value would save more with my map. Sebastian _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
