mesh portal discovery

[Benjamin M. Schwartz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Williams wrote:
> It's not that hard to write an app that notices and handles IP address
> changes.  Not handling this in apps that are written for or ported to
> the XO is just plain laziness.  When porting or writing, you need to
> handle the always-fullscreen-window case, you need to handle the
> security system, and you need to be aware of IP address changes.

No and yes.  I agree that this is the desired behavior, but it cannot be handled
by individual activities.  Correctly designed activities aren't even aware that
they are operating over an IP network.  Once Telepathy's streaming media support
is in, there will be almost no excuse to have the other participant's IP address
in your code, ever.

Telepathy must handle these network topology changes seamlessly, invisibly, and
entirely behind the abstraction barrier.  The routing system must be designed to
make this possible.

I know nothing about routing, but if a participant's IP address is about to
change, perhaps the change should be broadcast over the network, so that
Telepathy knows who to handoff the connection to.

- --Ben
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHhldgUJT6e6HFtqQRAgdeAJ9DPoCUaP9fOVINzxOu+/5BC7dYIQCfXF0L
IHwm7Z6q3q9g5x5T/+AKzQQ=
=3So0
-----END PGP SIGNATURE-----