Thanks a lot, I'll take a loot at this ORB.
Nico.
Leon Rosenberg a écrit :
Do you hold the data inmemory or in a file system?
In later case you'll be just fine with mounting a common share, like NFS
or SMB.
In first case you'd need a software synchronization inbetween, which is
typically so
Do you hold the data inmemory or in a file system?
In later case you'll be just fine with mounting a common share, like NFS
or SMB.
In first case you'd need a software synchronization inbetween, which is
typically solved by a publisher/subscriber pattern. You can use MDB
(message-driven beans, th
Oracle is the only aproved database (clusterable or not). This is the
reason I was looking for a "rsync"-linke solution.
Nico.
delbd a écrit :
Le Lundi 13 Juin 2005 14:27, Nicolas De Loof a écrit :
Our customer defines architecture restriction for it's applications. One
of them is that
Le Lundi 13 Juin 2005 14:27, Nicolas De Loof a écrit :
> Our customer defines architecture restriction for it's applications. One
> of them is that the (only) usable database is Oracle. As we don't use a
> database for the app, adding orcale only to get DB replication may be
> difficult to explain
Our customer defines architecture restriction for it's applications. One
of them is that the (only) usable database is Oracle. As we don't use a
database for the app, adding orcale only to get DB replication may be
difficult to explain (and will add a significant cost)
delbd a écrit :
Just
Just my two cents
I'll suggest storing the datas on a central database (which could be clustered
amongst your servers)
Le Lundi 13 Juin 2005 14:06, Nicolas De Loof a écrit :
> Hi all,
>
> this mail is totaly of topic, so sory sory sory...
> ... but there is so much java masters on this list !
>
6 matches
Mail list logo
