I've been using Groove the application for about 6 months and find it invaluable to collaborate on projects with small teams. It's file sharing, chat, security and replication are so brain-dead simple that I've gotten many diverse groups and running very faster than you could spell Intranet. Thus inspired, I looked more into Groove the platform for P2P app delivery. Specifically, I looked into trying to write some code that would ride on top of their APIs so that I could deliver a better photo-sharing app to end-users. It wasn't a very straightforward process, and non-crossplatform COM is a major turn-off. A very approachable compromise would be to use Groove's file sharing to distribute Rebol scripts with embedded data. I started prototyping something like this to deliver a photo-browsing View application, embedding JPGs into my REBOL files (so I didn't have to deal with Groove's storage API). As much as I would like the architectural cleanliness of a REBOL-only solution, using Groove to bootstrap a subset of Link functionality was pretty attractive. I think under this scenario you'd only be on the hook for the View run-time licenses. Since it's not really clear how Groove will treat either small developers or alternate platforms in terms of pricing, licensing and development roadmap, I would hesitate to code anything that relies any more heavily on that platform. JS [EMAIL PROTECTED] http://www.pobox.com/~johnseq 5/11/01 1:22:51 PM, Porter Woodward <[EMAIL PROTECTED]> wrote: >Hey - > >I'm sure some of you are already on the loop on this. But, have you all >had a chance to check out Groove? While it is Windows only (right now) I >would urge you all to try and take a look. > >"Groove software lets you create secure shared spaces wher you make >instant and direct online connections with others to share information and >get things done..." > >"The Groove client and platform reside securely on the individual's PC, >not on a Web site or server, giving users control over how, when and with >whom they interact. The Groove client includes tools for voice, and >text-based communications, file sharing, and many other interactive >activities, while the Groove platform supports standard development >languages, built in security and an XML code base, making it easy to build >additional tools as needed..." > >In short, it's pretty slick. The entirety of a shared space (all files, >messages, pictures, sketchpads, notepads, outlines, etc) resides on the >hard-disk of every participant of the shared space. It is secure both >on-the-wire and on-disk (ie. encrypted). It uses the exchange of public >keys to enable secure, instant messaging - as well as the exchange of >changes to the shared space. > >I have the sneaking suspicion that one could do some of this with >Rebol/View/Pro (encryption is a must). Groove is currently based on COM - >which despite their developer docs to the contrary - is still pretty much >a Windows only technology. Almost all of the "tools" in a space are built >around standard COM objects, or around the framework of COM objects that >Groove provides. So - like I said, some of this sort of thing could >certainly be done with Rebol/View/Pro; even more could be done if you >simply leveraged the COM objects they already provide - but then you would >loose most of the cross-platform capability that Rebol provides. > >Please, everyone who is able - take a look at: > > http://www.groove.net/ > > > >- Porter Woodward > >-- >To unsubscribe from this list, please send an email to >[EMAIL PROTECTED] with "unsubscribe" in the >subject, without the quotes. > > > -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
