[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers] savannah.gnu.org: submission of RubiCTM
From: |
anany |
Subject: |
[Savannah-hackers] savannah.gnu.org: submission of RubiCTM |
Date: |
Thu, 15 Nov 2001 12:21:36 -0500 |
A package was submitted to savannah.gnu.org.
This mail was sent to address@hidden, address@hidden
Tobias DiPasquale <address@hidden> described the package as follows:
License: gpl
Other License:
Package: RubiCTM
System name: rubictm
This package does NOT want to apply for inclusion in the GNU project
Rubi CTM is a Component Transaction Monitor written in Ruby, for Ruby. It will
implement server-managed persistence, transactions and security and will
integrate messaging and XML-based RPC (via SOAP) capabilities, along with
normal RPC connection technology.
Basically, this project is attempts to create a distributed object architecture
for the Ruby language that will allow Ruby to compete in the enterprise with
such technologies as CORBA, EJB and DCOM/COM+. As such, it will attempt to
incorporate currently-demanded technologies such as message-oriented
middleware, distributed transaction processing and object request brokerage.
Also, a naming and directory service will have to be established, as no Ruby
module exists for this sort of operation currently.
RubiCTM will (hopefully) be implemented in 100% pure Ruby (no C libraries for
RubiCTM itself), but may rely on some packages that rely on C libraries. This
is in an attempt to make it run on as many platforms as possible.
Also, a great concern will be for documentation of the APIs and ease of use for
the average developer, and may lead to subprojects: either some sort of
integration with an existing IDE (Emacs would be a good start), or a whole
development environment all its own (to be avoided , if possible).
RubiCTM will create an enterprise-ready platform to do distributed component
collaboration, while still retaining the power and ease of the Ruby language.
That is its main goal.