[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELisp as a generic COM Client?
From: |
Kevin Rodgers |
Subject: |
Re: ELisp as a generic COM Client? |
Date: |
Wed, 03 Sep 2003 15:01:51 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 |
Siegfried Heintze wrote:
Has anyone enhanced ELisp to make it a generic COM client? Perl has this
feature and elisp seems like a good candidate?
Really? From http://grc.com/dcom/
The strange history of DCOM
Many years ago, Microsoft began modularizing Windows and their
Windows applications by breaking them into functional components
with well-defined, "version safe" interfaces. The idea was to
allow pieces of Windows and applications to inter-operate.
The name first given to this effort was "OLE", which stood for
Object Linking and Embedding. OLE suffered nearly terminal
birthing pains and developed a reputation for being a bad
idea. Undaunted, Microsoft renamed it COM for "Component Object
Model". This was still the same old OLE, but Microsoft appeared
to hope no one would notice. COM fared somewhat better, but it
wasn't until Microsoft gave it the sexy name "ActiveX", and
built it into virtually everything, that developers finally gave
up trying not to use it.
--
Kevin Rodgers