I'm sorry for using an acronym that is not in vogue. Indeed RIA stands for
Rich Internet Applications - applications running within web browsers. Maybe
using AJAX or open laszlo.
My idea is (in order of priority):
1. Develop a "Rich" interface to subversion
2. Develop some sort of layer with a "plugin" architecture where one
can "plug" different versioning systems at the backend, but the interface
remains unchanged i.e. same interface to all popular versioning
systems. Apache with its modules is very close to my vision.
3. Develop a monitoring and managment framework for all these
4. Expose all this functionality as a service - as in Service Oriented
Do you have any similar projects going on? Any resources? I searched through
the mailing list archieves but could not find any.
Further, there is no "design specification" in the documents->design
section. I would like to have a copy of that document. Any ideas where I can
On 1/31/06, Ben Collins-Sussman <email@example.com> wrote:
> On 1/31/06, Sanket Sharma <firstname.lastname@example.org> wrote:
> > Hi,
> > I'm working on a RIA based interface to subversion. I would like to know
> > anyone is already working on something similar? I welcome any
> > recommendations and resources.
> I apologize for not knowing what "RIA" means... google says "Rich
> Internet Application". Is that just another acronym to describe
> applications-running-within-web-browsers, like so many of google's
> AJAX apps?
> And... what sort of application do you plan to write? What will it do?
Received on Tue Jan 31 17:49:42 2006