COM+ and Remoting

dotnet framework

    Sponsored Links

    Next

  • 1. Stupid people that sit at computers all day for 50k
    COBLS reg keys, recycle bin vnc they have delusions of grandeur becuase it's the burbank library it's only a 1 or a zero recover it on boot up. fire them all and give the money to school teachers who deserve it.
  • 2. !!!!!!!!!!!!!!!!!!!! WAREZ 4 SALE !!!!!!!!!!!!!!!!!!!! ?28268
    Software for sale. Huge Selection. 10 Euros/CD. Worldwide shipping. Windows, Mac, and Linux. The very latest software, stock video/photo, etc. Contact David for details: XXXX@XXXXX.COM tUY#T\t,PgQ:i64dDbJQ$QdZytBh9+%8Vo;%6^U/2j<

COM+ and Remoting

Postby Jason B » Sat, 04 Oct 2003 08:59:47 GMT

I haven't dug very far into remoting yet and I'm wondering if Remoting as
the same features as COM+ (queuing, pooling, transactions) or is Remoting a
whole different distributed computing animal separate from what COM+ tries
to achieve?

Thanks,
Jason



Re: COM+ and Remoting

Postby yubowen » Sat, 18 Oct 2003 22:34:35 GMT

Remoting is the alternative to DCom not for Com+.So I think it will not
support queuing pooling transactions and so on.
"Jason B" < XXXX@XXXXX.COM > 
: XXXX@XXXXX.COM ...
a



Similar Threads:

1.dcom vs com+ vs remoting

Hello.

I am doing a research on dcom, com+ and remoting.

We are about to develop a web application consisting 3 tiers ( web server,
application server, db server )

We are going to develop front end in asp.net and ms sql in the back end.

The middle tier mostly will be grabbing data from the db and give the result
to the front end.

I'd like to know what would be the better way to do this.

Should I use only one object in the middle tier that communicate to all the
threads requested from the web server? ( i'd like to know the pres and
cons )

I heard that dcom is better than com+ in particular situation so I'd like to
know in what situation remoting would be the best fit in the middle tier and
why

Thanx in advance


2.COM+ and Remoting

Hi Dot net gurus..
Can I access a COM+ component in an application running on different
machine? How can I do this?
Can I use .NET remoting for this? what are the design issues I should
consider when accessing COM+ components using .NET remoting? what other
options I have if I want my components to be accessed by applications
running on other machines?

Please help me... this is urgent..

-- 
regards,
Ashish Sheth


3.COM and Remoting

I am having the following problem using 1.1 Framwork. Before moving to 2.0 I 
would like to know if anyone had the same kind of problem!

I have a class A which uses a COM component (third party, so it can't be 
changed). This A class comunicates with another another class, B. This is a 
bi-directional comunication (B calls a method of A which, then, calls a 
method of the COM component).
Everything works fine until I the comunication between A and B is done 
through remoting.

When B resides in an application server the comunication between A and B 
works fine but when B calls a method of the COM component the system hangs. 
I have no idea of why this happens!

Thank you!

Rogio Manente
 XXXX@XXXXX.COM  


4.COM+ to Remoting Transition

We are a corporate shop that builds apps to run behind the firewall. In the
"Visual Studio Classic" world, we had used COM+ to host mid-tier components,
the primary purpose of these components to communicate with the SQL Sever
back end and return data.

Our clients are authenticated to run the app via Integrated Windows
authentication. Their captured credentials then allow them to run components
hosted by COM+.  The COM+ application is run under a domain identity that is
used to authenticate to SQL Server (we use Integrated Security=SSPI in the
SQL Server connection strings). So, in effect, the component executes based
on the calling users credentials, but makes data calls on that users behalf
using its own identity to talk to the db.

This has worked quite well for us in that we don't need to watch out for
exceeding our SQL Server licensing, and the identity used to access
production data is in one place and secure, known only to a select few
people. Our auditors seem happy with this approach, too. (We use a similar
type identity scheme for our development and test environments).

My question: How can we build a remoting environment (SAO, Single Call,
hosted in IIS) that allows us the same transparency as to identity passed to
the db? We really don't want to have the db access credentials sitting in a
bunch of web.config files. Granted, access to these can be limited, but it
still leaves a lot of maintenance should we have to start changing
passwords.

Has anyone had to encounter these transitional issues? There's absolutely no
literature out there that deals with it.

We would be very interested in what y'all have to offer.

TIA,
Bill


5.State COM+ and remoting

6. COM+ and Remoting

7. COM and Remoting

8. COM+ Web Services (ie remoting com+ from IIS)



Return to dotnet framework

 

Who is online

Users browsing this forum: No registered users and 82 guest