Just to be clear on my use case. I am not trying to build distributed objects. I am building an object management layer similar to what EOF/WebObjects was. The purpose is to expose in the client a graph of object for display and edition. The purpose of this is to simplify writing client side application by providing two main services: progressive loading of the object graph and change management.
Progressive loading is the ability to load objects as they are displayed in the UI including following relation between objects. "Real" object are replacing "proxy" objects as needed. The key is to maintain a graph of unique objects and to prevent leaks. Only objects retain by the UI should be kept in memory any object that is not displayed and does not participate in the object graph is candidate for GC. The change management is the ability to track changes to the objects as they occurs and to be able to identify all the insertion, changes and deletion on the graph so that the developer can commit all his changes in one operation. These concept are not new. They have been successfully tested and implemented over the years. All of iTunes and the Apple store is build on this. A lot of iOS application use CoreData that uses the same model. If we want user to build interesting application with our technology we need to provide the services that will enable them to focus on the business and not the CS. Our team know how to build that layer but to make it really compelling we need WeakRef. _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
