![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
At 06:19 14.12.99 -0800, Kent Crispin wrote:
> > > >Application layer. > Not in my 5-line client, it's not. > Source/destination address choice inside whois? inside finger? NO.
That was a flip remark for entertainment purposes, and it begs the question of what you mean, precisely, by "application layer" in a non ISO world.
to me, it's where different purposes do different things.
That being said, it would be straightforward to bury something like this in libraries, so your 5 line application just loads with the multihoming library code, which would be, in practical terms, an integrated resolver/socket library that cached performance metrics for IP addresses associated with a particular domain name, and automatically switched to different IP addresses when performance became bad. You would want to have it periodically ping the other addresses, as well.
Socket library/DLL, I can live with.
I'm not proposing from a position of advocacy, you understand, but from a pure implementation point of view, it seems straightforward, and you could easily write 5 line clients that used it.
Understood.
Harald
-- Harald Tveit Alvestrand, EDB Maxware, Norway Harald.Alvestrand at edb.maxware.no
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.