Hi Brad
[quoted text, click to view] > Valmir,
> You ask a good question - is there a need to put your dll in COM+?
> Unfortunately, that's not a question I can answer since I don't know the
> goals of your application & its requirements.
It's simple: The user type their vehicle registration ID. The component
connects to a third machine (you called it 'box') where resides a 'manager'
(actually, a NT service). This NT service opens a connection through TCP/IP
socket with a Unisys MX series mainframe, get some data about the vehicle
(like bills, non payed taxes, etc) and give them back to the component
[quoted text, click to view] > Do you need any of the services offered by COM+? Transaction support,
JIT,
> Synchronization, object pooling, etc. ? If not, then there is likely no
> need for you to put your dll in a COM+ app.
Yes, I agree with you, there's nothing in the process described above that
needs transaction support, snchronization, pooling, etc.
[quoted text, click to view] > There are only two reasons in which one would put one's dlls in a COM+
> application without using any of the services provided by COM+:
> 1. Process isolation. You want your dll to run in its own process that
> is separate from the client's process.
Maybe proccess isolation would be a interesting issue. But there are few
access per day to this component. Maybe it'd soud like using a missel to
kill a fly
[quoted text, click to view] > 2. You want your code to run under the identity of a specific NT
account.
I think we don't, the service on the third machine only accept calls from
the web server ip address.
[quoted text, click to view] >
> HTH,
> Brad
Thanks very much, Merry Christmas and Happy News Eve!
--
---------------
Valmir Cinquini
Cidadania Italiana: visite
http://www.cinquini.com.br Banda larga de 1º mundo: Visite
http://speedy.bravehost.com/speedy.htm Lista MS-SQL:
http://br.groups.yahoo.com/group/mssql-pt/join
Lista C#:
http://br.groups.yahoo.com/group/csharp-pt/join
