|
|
Posted by Steve on 09/12/07 02:07
> Those are all Microsoft thingies.
again sanders, if you don't know what the fuck you're talking about, why the
hell would you announce it to the world as if you did know?
> COM is the Component Object Model - a version of the Windows Foundation
> Classes.
well, you got the achronym right anyway.
> DCOM is distributed COM - a patchwork add-on of Win95 that was added
> because when 95 came out, MS had not considered certain internet
> implications.
holy fucking shit! you really have no clue here!!!
> .NET is MS's latest attempt to build an all-in-one,
> everything-to-everybody architecture.
again, further proof you have no fucking clue.
..net is an architectural redesign and implementation of what com tries to
achieve...however the scope is much more broad than that since ms hopes to
reach complete platform independence with its use. it is also birthed in the
dispute(s) between sun microsystems and ms and ms' use of what once was
their version of java virtual machine.
if you didn't know any of that (which is quite obviously the case), you
could have at least either kept your yap shut or even googled just a bit
more and found out. but i suppose you love the taste of your own feet.
>> And DCOM... that one seems like it might be a COM file put
>> into a publicly accessible folder, but I'll need some more
>> help here, if such is available, because something is not
>> sitting too well here.
dcom is similar to com but allows for remote instanciation of objects
(similar to remote procedure calls)...and by remote, i mean creating/using
com objects on a completely different server. that's not the end of it, but
that is where i'm leaving it.
now back to you, sanders...get a clue!
Navigation:
[Reply to this message]
|