 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Radu B.
Guest
|
 Posted: Fri May 18, 2007 7:50 pm Post subject: DCOM vs. CORBA |
 |
|
Hi there,
I have an n-tier app build with D6. The connection to then
application server is either DCOM or CORBA depending on how the
application is build.
Both builds, are created with MultiInstance/MultiThreading flags.
First of all, I don't clearly undestand that if I have the RDM
created with MultiInstance flag set, all the clients connected to the application got their own instance with all of its
objects, meaning that there is no interferece between objects
belonging to different clients, or isn't it?
Then, I experience the following problems:
the DCOM executable serialize the requests, meaning, if an
client starts a time consuming procedure, all the other clients
are waiting for the former to complete, and this is a major
drawback - in contrast with CORBA which permits to the others to
work (all of interrogations are against a sql server which
controls the flow of transactions);
the pros of DCOM are that all the exceptions are raised clearly
to the client side - in contrast with CORBA where you got only
"Catastrophic failure" - and if a connection is lost (even
behind a firewall of a ruter), after a reasonable period of time
(usually 10'), the connection is closed by DCOM itself, in this
way freeing the memory - in contrast with CORBA where the
connection remains active and a new one it is not possible,
getting the message "Connecting to CORBA..." and I have to
restart the executable.
Now I want to combine the pros but I don't have sufficient
knowlodge to do this...
Can anyone help me?
Thank you |
|
| Back to top |
|
 |
Farshad
Guest
|
| Posted: Fri May 18, 2007 11:50 pm Post subject: Re: DCOM vs. CORBA |
|
|
"Radu B."
| Quote: | Then, I experience the following problems:
the DCOM executable serialize the requests, meaning, if an
client starts a time consuming procedure, all the other clients
are waiting for the former to complete, and this is a major
drawback -
|
Actually, DCOM has nothing to do with this. I think there is something wrong
with your threading model. What threading model are you using?
Check the initialization part of your code in RemoteDataModule unit:
TComponentFactory.Create(ComServer, TX, Class_X, ciMultiInstance,
tmApartment);
It seems that you are using tmSingle for threading model. |
|
| Back to top |
|
|
Radu B.
Guest
|
| Posted: Sat May 19, 2007 2:51 am Post subject: Re: DCOM vs. CORBA |
|
|
| Quote: | Actually, DCOM has nothing to do with this. I think there is something
wrong
with your threading model. What threading model are you using?
Check the initialization part of your code in RemoteDataModule unit:
TComponentFactory.Create(ComServer, TX, Class_X, ciMultiInstance,
tmApartment);
It seems that you are using tmSingle for threading model.
|
Unfortunately, "Both builds, are created with MultiInstance/MultiThreading flags."
In initialization section I have
"TComponentFactory.Create(ComServer, TSferaSrv, Class_SferaSrv, ciMultiInstance, tmFree);"
for DCOM
and
"TCorbaVclComponentFactory.Create('SferaSrvFactory','SferaSrv','IDL:SferaAppServer/SferaSrvFactory:1.0',
ISferaSrv,TSferaSrv,iMultiInstance,tmMultiThreaded);"
for CORBA |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
