Comments on: Wave needs a decent client http://www.certpal.com/blogs/2009/11/wave-needs-a-decent-client/ Technology and certifications Wed, 28 Jul 2010 06:39:33 +0000 hourly 1 http://wordpress.org/?v=3.0 By: CertPal http://www.certpal.com/blogs/2009/11/wave-needs-a-decent-client/comment-page-1/#comment-1023 CertPal Thu, 10 Dec 2009 06:04:46 +0000 http://www.certpal.com/blogs/?p=469#comment-1023 <a href="#comment-1020" rel="nofollow">@John Poole </a> Yep the persistence was a pain point as well. Thanks for bringing that out. We need a server that can persist, scale and serve rich clients. Still a long way to go. @John Poole
Yep the persistence was a pain point as well. Thanks for bringing that out. We need a server that can persist, scale and serve rich clients. Still a long way to go.

]]> By: John Poole http://www.certpal.com/blogs/2009/11/wave-needs-a-decent-client/comment-page-1/#comment-1020 John Poole Wed, 09 Dec 2009 03:54:48 +0000 http://www.certpal.com/blogs/?p=469#comment-1020 Comparing wave to the telephone system. Google has released the code to create a telephone exchange, but they have kept the telephones (e.g. the GUI clients) closed. A telephone exchange is not much use to most users unless you have an acceptable client to connect to it. Let us not forget that the server they have released does not store the Waves it creates in a permanent sense. When the server goes down, everything will be lost. So the server without a working database to preserve the data between interruptions really is something of novelty for a developer to study, but cannot be of much use to try out with users. You don't want users to suddenly lose their content. Give us: 1) a GUI client and 2) permanency of the wave data and then we can really conscript users to test and we can invest our time developing. Comparing wave to the telephone system. Google has released the code to create a telephone exchange, but they have kept the telephones (e.g. the GUI clients) closed. A telephone exchange is not much use to most users unless you have an acceptable client to connect to it.

Let us not forget that the server they have released does not store the Waves it creates in a permanent sense. When the server goes down, everything will be lost. So the server without a working database to preserve the data between interruptions really is something of novelty for a developer to study, but cannot be of much use to try out with users. You don’t want users to suddenly lose their content.

Give us: 1) a GUI client and 2) permanency of the wave data and then we can really conscript users to test and we can invest our time developing.

]]>