>I'm advocating merely that traditional wave development, specifically >standardising and documenting the c/s good point
>separately to any >discussions and future plans regarding new server protocols. +1 productive discussion is going already, from the very beginning of this topic and now - according to what was proposed and asked in this discussion, all non Apache, yet Wave servers developers (except lightwave's but Joseph is represented him directly as they are friends and working together in some areas) already participated on http://primarypad.com/OeMj2ZnZqo Call or it's mirror, that leaded to ongoing formalizing of XCCC afford with Kune's and ourproject.org resources. >I see p2p as a complete separate project. Like "futurewave" or >"bluesky super protocol" or something. i can only merely agree on this - because - as Paul Thomas said: >I think if anything cloud technology will >be involved with wave. we can forget about p2p distributive extensions and just use AppEngine or other free storage to start, we can forget about p2p distributive computing or - better - if you'd ask me -- make the main of it in extensions standard, depending on - if some AI developers or EvoGrid folks would be really interested in near future, but - distributive persistence scheme is so widely used and so developed now, and is base for most of what's called Cloud everywhere (in my view - cloud is like distributive DBs and computing but under authoritarian HQ, that what GNU in the way of Richard Stallman - against, compared to real distributive like Tahoe-LAFS kind of 'cloud' systems) that we shouldn't say NO to it, before it will be widely discussed with all XCCC participants, at least.
