[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-255) Remoting capabilities

[Emmanuel Bernard (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-255?page=comments#action_25579 ] 

Emmanuel Bernard commented on EJB-255:
--------------------------------------

Hi Dimitry
Of course you can tunnel your JDBC calls through whatever protocol you want, so the firewalls is not the issue, neither is the communication breach since it can be crypted. Note that those problems are *exactly* the same for a remote EM. You somehow need a key/password on the client side to communicate safely to the server, be it remote EM or remote JDBC so both need configuration.

As for business security (what you call service method security): if you open the EM, you have access to all operations available on mapped objects, this is very close to what you can do in plain JDBC (esp since the EM can give you back access to JDBC anyway). True business methods, with limited operations are interesting for security but then you no longer need a remote EM.

Transactions issues would be fine if Hibernate was used locally with a remote JDBC call, this is solved by the conversation scoped persistence context. I don't see the benefit to create a delta object change mechanism (this is already what Hibernate do when it talks to the DB :-) )

joins transfers more data than a PC diff, but it also requires to keep a copy of this PC at the server side hence consume more resources, plus using a Persistence Context + lazy loading  + subselect + batch-size minimise those issues, this is not an obvious choice :-)

SCA seems to suffer from the reinventing the wheel syndrome to me, I don't have strong opinions on SDO, though.

I'm not saying that a remote PC is a bad idea, I'm saying that it's not as good as it first sounds, and the good usecases are not that large. I reckon the traffic size and latency is something that needs to be addressed. I tend to like XUL over NetBeans/Eclipse as a rich platform approach, but I'm not an expert in that field.

Good talk.


> Remoting capabilities
> ---------------------
>
>          Key: EJB-255
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-255
>      Project: Hibernate Entity Manager
>         Type: New Feature

>     Reporter: Dimitry Voytenko

>
>
> I came across Kodo's implementation of remote persistent managers for both JPA and JDO:
> http://www.solarmetric.com/Software/Documentation/3.2.0RC2/docs/ref_guide_remote.html
> http://www.solarmetric.com/Software/Documentation/3.2.0RC2/docs/ref_guide_remotepm.html
> The solution looks pretty ellegant. The main idea behind it is that server and client communicate b/w each other using object graphs (no proxies and no object serialization required) and thus working with JDO/JPA objects on client looks exactly the same as on the server, removing necessity of DTO objects in the majority of cases.
> Have you ever thought about including similar functionality for Hibernate? I do believe it could be a great peformance booster for many types of applications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira