🚀 go-pugleaf

"Andrue Cope [TeamB]" <no.spam@not.a.valid.address> �crivait news:43ba763b
$1@newsgroups.borland.com:

> Alan Bellingham wrote:
> 
>> I'd say that that would be when to make it a COM server. Then you can
>> have arbitrarily complicated types, with multiple language support.
>> 
> 
> Good point, actually.
> 
>> COM may not be the most elegant possible solution, but at least it's
>> got defined rules, and it usually works quite well. It's just a pain
>> coding it up in the first place (says he who has just created a 48K
>> type library with several dozen interfaces and who now needs to
>> actually write some code to go behind it).
> 
> Lol. We use COM but luckily the BCB wizards did everything for us and
> they did it right. I /still/ have almost no idea how it works :)
> 

thanx for your responses.

in fact, theses datas are available on a server (workstation1), I have 3 
clients (.exe built under BCB6.0 Pro) on the same workstation2 
(communication protocol = Ace Tao CORBA), each one loads locally about 
400/500 Mo of datas, because these are "real-time" clients, they need to 
access instantly to datas.

it works fine actually, but the workstation2 needs at least 2Go of RAM.

so I just wandered if sharing datas in memory into a common dll on 
workstation2 would be a solution which needs only 1Go of RAM ???