On 7/19/13 10:30 AM, Sebastian Kiesel wrote: > Sure. I know these paragraphs. But these would be compatible with all > of the three definition approaches in my original mail (see below). > So I am wondering whether we need a more precise definition. What is > the unique thing that defines an individual ALTO server? The single IRD, > the single network map, ...?
I may be missing something, but I actually don't get what we'd gain in redefining concepts that are very common to most protocols, and in particular to HTTP that ALTO builds on. To turn the question around, what's the server when you open a web URL in your browser? The L2 load balancer in front of the datacenter that you'll hit first? The chain of reverse proxies you're likely going to hit? The worker process putting together the biggest amount of bytes that will go in the HTTP response you'll get in return? The virtual machine on which such process runs? The physical box? Again, I may be missing something, but this looks like a slippery slope I'd rather not go to.. Enrico
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
