Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://objectstyle.org/jira/secure/ViewIssue.jspa?key=CAY-264
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CAY-264
Summary: Design of Remote Nested DataContexts (i.e. like Java Client in WebObjects)
Type: New Feature
Status: Assigned
Priority: Major
Project: Cayenne
Components:
Cayenne Core Library
Versions:
1.2 [DEV]
Assignee: Andrus Adamchik
Reporter: Ashley Aitken
Created: Thu, 27 Jan 2005 10:21 AM
Updated: Thu, 27 Jan 2005 10:21 AM
Environment: NA
Description:
Hello Cayenne Developers,
I understand that you may be considering extending Cayenne to allow nested data contexts (excuse me if I use EOF terminology) and remote data contexts (like Java client in WebObjects) or something like that for the next version.
If you are then I would like to politely request some features, and offer some issues for you to consider in your design please. These relate mostly to the remote data contexts, but as they are often implemented via nested data contexts this may pertain also to them, and some to any data contexts..
I hope you can make something of this unstructured set of comments:
A lot of Web apps work with few business objects, customer, shopping cart, etc. However, some Web application work with a much larger number of business objects.
Please consider making Cayenne scale as well as possible with regards to the number of business objects. Particularly, if some business objects are (so far) read-only (or even could be marked read-only) it would be great if they could be almost as efficient as POJOs. Of course, there is the need for "uniquing" but besides that ...
A lot of web apps just use a browser interface. However, I believe in the future, rich client applications will become more important, especially inside the enterprise.
Please try to ensure that the differences between a nested data context on the server (in the same process as its parent data context) and a remote client nested data context are small. Of course, performance will be different, but functionally it would be great if they were almost (if not entirely) the same.
Rich client applications with data contexts on the client may need to transfer a lot of objects back and forth and may need to work off-line.
Please try to ensure that the communication between the client and server is as efficient as possible (or alternatively allow it to be customised, compressed, encrypted like EOF does). As well, please try to ensure there is some way of working off-line with the rich client (if this is at all possible) and then reconnecting when back on-line.
The latter is something like detached data contexts, i.e. data context that no longer (or temporarily) don't have access to their parent data context or data store.
Again, these are just some suggestions. Of course, I am grateful for anything you do. If you can just keep these in mind for the future design of Cayenne that would be great. I wish I had more time (and more ability) to be able to assist with the development (or surrounding work).
Best regards,
Ashley Aitken.
mrhatke..ac.com
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://objectstyle.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
This archive was generated by hypermail 2.0.0 : Thu Jan 27 2005 - 10:22:31 EST