>>>>>>COM is a Winders thing.. but, if you want to run a com component you can set up a seperate Win/NT workstation or server to run your COM servers... also, if your COM servers crash windows you don't loose NetWork services.
>>>>>>
>>>>>
>>>>>There is limited support available to allow native ?nix apps access DCOM services, but there's no capability of hosting COM or DCOM using native Linux code, or running a Win32 COM component AFAIK. Certainly not one of the emulators.
>>>>
>>>>Isn't that what I said? I said (see above) if you want to run a COM component, you have to do it on a windows machine.
>>>
>>>The problem is "COM is a Winders thing"; there is limited COM support for ?nix froma COM client perspective certainly, and since DCOM is basically a set of interfaces whose implementation si completely hidden from the client, a very talented programmer could create a Linux native app that responded to and behaved as a COM server in a DCOM environment; a major PITA, but at least in theory it's doable.
>>>
>>>But we agree completely, VFP stuff won't run under Linux, and neither would standard Win32 COM servers.
>>
>>I'm still not able to understand com and dcomm...
>>
>>can u pls give example of any such application...
>
>I don't understand what you're asking. You'd use DCOM from a Unix client in exactly the same situations that you'd use DCOM from a Win32 client - you want to access services from a server using the COM interface model, and that server happens to not be running on your system.
>
>COM is a mechanism for publishing a set of services through a publicly defined interface, consisting of visible methods and proiperties, where the internal workings are concealed beneath the public interface. You use the methods and properties to access the underlying functionality without having the server's internal workings exposed and visible in detail to the client making the request.
>
>COM provides a set of standard mechanisms that allow the client to explore the exact nature of the interface at runtime using a common set of services. DCOM is nothing more than a mechanism for making a COM interface available for a server process running on a machine other than the local client; it allows you to explore and access the interface in the same way that you would if the COM server were running within your process' memory space, or on your system as a separate process. From the client app programmer's POV, it doesn't matter where it runs.

Sorry to bother you again... but I'm very new to these terms... Theoritically i've understood little bit... But can u pls Tell me any Programs / Softwares which uses this mechanism....

I'm asking this bcos I want to chk whether I'll be using any of these in my future projects...

Plus pls tell me any sites / help file where I can get additional info. abt. that...

TIA