Main Page
From Rvooz
Contents |
Welcome to the rVooz wiki.
- Demos
- Download
- Documentation
- FAQ
- Features
- Participate
- Mailing Lists
- Source Code
- The Team
- irc://irc.freenode.net/rvooz
The Pieces of the rVooz Ecosystem
Here's a quick overview in PowerPoint form: rVooz_Overview.ppt
The Gateway
The Gateway service accepts registrations via its REST interface, and feeds context "jobs" to pluggable matchers. The Gateway also consumes contextions produced by Matching Engines.
Gateway
Matching Engines
Matching Engines do the real work in the rVooz system, making matches between users based on any given context. Currently we are working on a Geo Matcher that can figure out the closest person to your location, and a String Matcher that can compare just about anything.
Geo-Matcher
String-Matcher
Voozers
Voozers are software devices that consume a "contextion" from the rVooz Gateway and proceed to provide a link between multiple users at an IM or VoIP application (or any communication app).
Openfire-Voozer
Clients
Geo-Client
Eclipse-Client
REST Interfaces
To interact with a rVooz Gateway service, send simple HTTP requests to the server. Sending a "context" message to the Context interface registers with the service. Sending a request to the Contextions interface will return, yes you guessed, a list of contextions - based on the rules provided in the request. For example, it is possible to register a geo-location context, then request on the Contextions interface for the closest match.
Architecture
If you want a better understanding of how all the pieces in the rVooz pie work together, check out the link below.
Architecture
Developer Guidelines
With different languages and frameworks making up rVooz it is difficult to point to a specific style guide. But, there are many other commonly shared best practices across the rVooz ecosystem that we capture in our developer guidelines.
