[nylug-talk] Why does "enterprise" imply "Java"?

[Felix Shnir]

Ajai, j2ee has stuff that for you to understand you need to phrase it "ohh
of course, its DRb in ruby!"

Well, j2ee has em from the get go.  When you install j2ee application server
- all of this stuff is there already.  You are able to read docs and build
distro environment.  Also, you are not required to have intimate knowledge
of any of the APIs.  You need to know that they are there, and need to know
what they are used for.  When you store an object in JNDI - you need to know
nothing about how / where this tree is stored and who maintains it.  You
just need to know that its there, and you can access it.  Lastly, server
administrators are ultimately the ones that have control over scalability
and distribution -- developer only manager logic in the objects, but admins
have ability to spread the load in any way they see fit -- wonna move the
heavy hit enterprise beans to a better server?, no problem, increase
database pool? -- all in the entrprise consoles...

Its the same thing with all of the APIs that are in the j2ee pool...

Felix.


On 7/7/06, Ajai Khattri <ajai at bitblit.net> wrote:
>
> Felix Shnir wrote:
> > JNDI is a small part of J2EE stack... There are more "enterprise"
> > stuff in
> > there =)  But generally, what I was trying to say before, is that Java
> > allows and has APIs for things that neither PHP, Ruby, nor Python have
> > simply because they didnt need it.
>
>
> So basically, JNDI allows you to store and share objects across machines?
>
>
> Ruby/RoR applications can do something similar with memcached or DRb
> (distributed Ruby).
>
>
>
> --
> A
>
> _____________________________________________________________________________
> Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org
> The nylug-talk mailing list is at nylug-talk at nylug.org
> The list archive is at http://nylug.org/pipermail/nylug-talk
> To subscribe or unsubscribe: http://nylug.org/mailman/listinfo/nylug-talk
>