|
Posted by Bruce Eitman [eMVP] on November 9, 2007, 8:35 am
Please log in for more thread options Service has special meaning. I am beginning to think that you are applying
service to something that isn't really a service.
It seems to me that you have a DLL, nothing more than that. Not a service.
Since it isn't a service, you don't have the functionality defined or
managed for a service.
Is this correct?
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
> Sorry, let me try this again. I tried sounding like I knew what I was
> talking about, but that failed ;o. I'm new to the Windows
> Environment, please bear with me.
>
> I'm looking to create something similar to the RIL in terms of a proxy
> and a service. Clients (applications, services, drivers, etc) would
> link to the proxy dll to talk to the service through a set of APIs. A
> client would call something like RIL_Initialize to get a HANDLE, as
> well as set up callback functions, etc.
>
> I'm just wondering how I could figure out if a client that was
> registered successfully to my service and if that client's process was
> killed in Task Manager or if the client crashed, how could my service
> know so it could clean itself up? As you mention, if the process is
> no longer running the Deinit would be called automatically when my
> proxy dll was unloaded by the client? What component calls it? Is
> this different if the client is in the application layer? Or if the
> client is in the device.exe layer? or even in the services.exe layer
> itself?
>
> Hope that is a little better, I appreciate your help.
>
> - Joe
>
| 
XML Sitemap