I wouldn't worry too much about mobile devices. They're evolving very fast. Think a few years down the road.
In any case, signing on the client can be problematic for a different reason, namely that obtaining the certificate you need for signing is not a simple process at all. It will be too complicated for the majority of users. That has been discussed in the spam threads. Frankly, I'm not so sure it's really necessary. As long as the server is trusted (has a valid certificate etc), and the user is authenticated by that server, it should be enough. What is needed however, is a way for the client to get all the servers' signatures for a given delta and verify them. This needs to be supported by whatever C/S protocol that will be developed. On Oct 9, 8:59 pm, Stefan Langer <[email protected]> wrote: > I agree that any viable solution should support signing as not to go down > the same route email has taken. Just think about wave having a signal to > noise ratio of 85%. Signing might be a problem for mobile devices though. > > Has Google taken any part in this discussion yet as it will be likley that > if they open source their client it will be used as the base of the defautl > wave implementation --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
