Gregory Peres wrote: > > Standards are meant to be used as a guide line... They are not intended to > be a law. > > > From my understanding of CMP... It is to provide an object oriented > environment to develop an application that does not burdened me with the > pain of having to write SQL. When I think of working in a CMP environment > I dream of the ability to persist Entity Beans not just the "data". The > easiest way I know to make this dream a reality is with an OODBMS. Java is > about objects, NOT rows and columns. Until the general population > understands this we are not going to see anyone jump up to the real CMP > challenge: Seamless Object Persistence (I have seen too many vendors back > away from this already.) CMP would be easy to use (from a users standpoint) > if they could persist real objects and not fuss with a RDBMS at all. > (Dreaming here but, hey... I can! Today app servers already have this > ability in their products but hide it.) > > I am concerned with making flexible, scalable, distributed, fast, object > oriented applications. Not necessarily the portability of my code. If an > application server can provide me with an environment that allows me to do > this, in a timely manner - great! Why would I ever consider switching? Why > do I even care if my model is portable between products? It comes down to > the time old saying... Use the right tool for the right job. > I don't agree with you in this point... maybe switching is a good thing. This way you can make an application and sell it without worrying about things as load or scalability. These should be handled by the application server, so the company buying your software could choose from a variety of app servers based on their needs in number of users, load balancing, scalability, fault tolerance, availibility, etc. > > > Someone will probably say to use RDBMS because it is the "standard". Point > considered. Why not upgrade the standard to be objects? I think objects > would make an excellent standard. We all know the reason why we use RDBMS: > Our executives (Who by the way are technical geniuses!) read InfoWorld and > make us. > > Join the object revolution! Ok, I'd like to join :o) I consider myself an object purist too, and I don't understand certain things... it seems there's a real push in industry towards object oriented programming, you know, Java is becoming or even has becomed a standard, UML is all around, CORBA and RMI are making sockets to be just an inner layer that a few people remember,... but it doesn't seem to be such a push in object persistance... what happened to ODMG, are they still working? what about EJB? doesn't seem a back step with all that RDBMS feeling? Is there any initiative to provide EJB CMP in OODBMS, or integrate these two worlds?
begin:vcard n:Gonz�lez G�mez;Jos� tel;work:93 414 07 72 x-mozilla-html:FALSE url:www.cast-info.es org:Cast Info;Ingenier�a del software adr:;;Tusset 23, 1�;Barcelona;Barcelona;;Espa�a version:2.1 email;internet:[EMAIL PROTECTED] fn:Jos� Gonz�lez G�mez end:vcard
