[pypy-svn] rev 1942 - pypy/trunk/doc/funding

pedronis at codespeak.net pedronis at codespeak.net
Tue Oct 14 23:57:50 CEST 2003


Author: pedronis
Date: Tue Oct 14 23:57:49 2003
New Revision: 1942

Modified:
   pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
Log:
minor fixes: Java EJB -> RMI

Prevalance? I have'nt find a reference to such a package,
if it exists please restore.



Modified: pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.0_detailed_implementation.txt	(original)
+++ pypy/trunk/doc/funding/B6.0_detailed_implementation.txt	Tue Oct 14 23:57:49 2003
@@ -332,7 +332,7 @@
 
 We will study which of these implementations is best suited for being moved
 into the interpreter itself. These include transparent interfaces to remote
-objects (CORBA, Java EJB...), transparent distribution of objects, and
+objects (like CORBA, Java RMI...), transparent distribution of objects, and
 transparent distribution of processes themselves. For example, a foreseen
 solution for the CORBA model would be to design a proxying Object Space that
 delegates operations to a remote CORBA object server over the network, thus
@@ -348,16 +348,17 @@
 subject has been studied extensively, and there are several implementations
 already available.
 
-We are considering at this point ZODB, the Zope Database engine, and PyPerSyst
-and Prevalence, which are quite complete. Their respective developers have
-already expressed high interest in PyPy. Indeed, they would benefit from
-better language integration; they currently put non-natural constrains on the
-programmer in terms of what he is allowed to do for persistence to actually
-work transparenty. Typically, it is not possible for a library to detect
-changes such as adding elements to lists, so that list objects cannot be
-automatically marked as "dirty" (as needed to ensure they will transparently
-be saved when necessary). This requires language support, and more
-specifically an extension or proxy Object Space.
+We are considering at this point ZODB, the Zope Database engine, and
+PyPerSyst, which are quite complete. Their respective developers have
+already expressed high interest in PyPy. Indeed, they would benefit
+from better language integration; they currently put non-natural
+constrains on the programmer in terms of what he is allowed to do for
+persistence to actually work transparenty. Typically, it is not
+possible for a library to detect changes such as adding elements to
+lists, so that list objects cannot be automatically marked as "dirty"
+(as needed to ensure they will transparently be saved when
+necessary). This requires language support, and more specifically an
+extension or proxy Object Space.
 
 
 Language-level extensions


More information about the Pypy-commit mailing list