Hi If you don't need a service oriented architecture, this would be a really cool thing to have.
Pros: - development could be done with the non distributed Session, there would be no difference to a fat client architecture - client-server communication would be pluged in transparently when you switch to distributed Session, no need to write business delegates and DTOs - the second level cache is on the server, no need ot have a distributed one Cons: - the implementation of a distributed session cannot be done easily - maintaining a distributed session and non distributed one is a pain - as Max mentioned: transaction boundaries on the server are managed by the client BTW: An other approach of transparent client-server architecture would be to cut the GUI layer appart, things like RSWT (rswt.sourceforge.net), TerminalServer or Citrix. HTH Ernst --- Max Rydahl Andersen <[EMAIL PROTECTED]> schrieb: > Hi, > > I'm all for client/server-enabling Hibernate if it > was just this simple... > > ...but how do you mange transaction boundaries in > this setup ? > > Do you keep a transaction/connection open on the > serverside to the db for > the client ? or ? > > /max > > > On Wed, 17 Nov 2004 10:02:20 +0100, Marek Mosiewicz > > <[EMAIL PROTECTED]> wrote: > > > Hi > > > > Some time ago there was discussion here about > client side usage of > > Hibernate. > > > > I have been trying to adopt Hibernate to Compiere > > > (http://www.compiere.org) > > which is open source ERP system and I have this > problem there. > > Basicly there is client application there and > application server in > > Compiere. > > Currently it has two workingo modes. In one client > connects directly to > > database fro fetching data and second (secure) in > which client sends > > wrapped > > prepaded statment to application server which > checks for permissions > > (rewrites query to add additional WHERE clauses to > limit data). > > Second one is acctually only one solution there as > direct DB connection > > from > > untrusted client is disaster there. > > > > > > I have been thinking about imlementing secure > client feature into > > Hibernate. > > Session object colud be logically split into > client and server modules > > (in > > usual case there would be working as now). Client > side would be > > responsible > > for caching, change detection, resolving relations > etc. > > Server side module would execute queries and > updates and could apply > > mandatory filters on data. > > This solution could also give "connected" like > behaviour in client-server > > environment (which is main drawback of DTOs). > > That mean that client side would fetch additional > relations from server > > in > > necesssery (it would be important to fetch them in > some batches for > > performance) and reattach relations. > > It would impact some functionality like iterators > which in this case > > would > > be probably not possible and would decrease > performance when splited. > > Anyway in scenarios where client is untrusted or > there is only > > application > > server connection (no access to DB connection) it > would be great. > > > > What do You think about it ? > > > > > > Marek Mosiewicz > > http://www.jotel.com.pl > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: InterSystems > CACHE > > FREE OODBMS DOWNLOAD - A multidimensional database > that combines > > robust object and relational technologies, making > it a perfect match > > for Java, C++,COM, XML, ODBC and JDBC. > www.intersystems.com/match8 > > _______________________________________________ > > hibernate-devel mailing list > > [EMAIL PROTECTED] > > > ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
