Re: The Revenge of the Geeks

From: Arne Vajh°j <>
Date: Thu, 24 Jan 2013 22:15:27 -0500
Message-ID: <5101f8d3$0$293$>

On 1/24/2013 10:10 PM, BGB wrote:
> On 1/24/2013 4:58 PM, Arne Vajh°j wrote:
>> On 1/24/2013 5:10 PM, BGB wrote:

>>> On 1/24/2013 10:06 AM, Arne Vajh°j wrote:
>>>> On 1/23/2013 11:47 PM, BGB wrote:
>>>>> but, in any case, with the other languages there are a wide range of
>>>>> libraries available, many under fairly open licenses (like MIT or
>>>>> BSD),
>>>>> and there is a lot more GPL stuff available,
>>>> In the EE space you would need to look at CORBA or DCOM.
>>>> You would prefer Java EE believe me.
>>>> :-)
>>> errm, so you can't just copy all the files over to ones' servers? and/or
>>> recompile the code for ones' servers?...
>> The coding model in Java EE is definitely more modern than that
>> of CORBA and DCOM.
> I didn't mean like CORBA or DCOM, but probably directly copying over
> program binaries (DLLs or SOs and precompiled binaries and similar), and
> probably using traditional compilation and linking.

You lost me.

How to get the same type of services as Java EE provides is related to copying binaries how?

>>> as for data sharing (between lots of networked servers), I am less sure,
>>> I would think maybe something like NFS or SAMBA, but then thinking of
>>> it, NFS or Samba might not scale well if the number of servers becomes
>>> sufficiently large (like, people would probably want to locally cache
>>> files, rather than always doing IO over the network, ...).

>> Persistent data in the the Java EE world is most often in database.
> well, I meant for code and other resources.
> or, to you mean putting code in the database as well?...
> (like, put the JAR in a data-blob and fetch it out via a SELECT or
> something?...).


But as I said I am lost.

Arne Received on Fri Jan 25 2013 - 04:15:27 CET

Original text of this message