Hi Jay...
--On Wednesday, April 11, 2001 12:57 PM -0400 Jay Walters
<[EMAIL PROTECTED]> wrote:
> Besides, if you decide to change things, then change the unique ID
> generation. It's not as if you're just going to take an application that
> works with Oracle and plug it into a LDAP server or a message store.
> Sorry, I've never seen it. In any application that has been optimized in
> terms of data access there is always some database specific tuning
> involved and this likely won't work on the next one.
Most of your comments are quite correct for many uses and applications, in
particular, if your developing an app for use in house.
I think a concern for many people is that they want portability in their
app not so they can migrate from one platform to another after deployment,
although that may well be needed as systems grow, but so that they can
license the app and let the customer deploy the app in their own existing
environmant.
Many big companies have a signifigant investment in an infrastructure (and
entire departments to maintain this infrastructure), such as an Oracle
database system used by all the companies apps, or a mainframe system
everything must run on, and so on. If the app vendor can avoide
dependencies, they have a wider market they can serve with less effort.
If you don't know what your deploying on at design/development time (and
its often best to assume you don't) then you want to make sure your
components work in a wide variety of cases, including any database, and
server, clustered or non-clustered and so on.
My $0.02!
Jim
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
