I don't see why one would consider Win32 API a better architecture than
.NET.
My experience is different (I've been programming from 1986-87 or
something on
various languages and platforms including microprogramming and bytecoding
by
hand)
It's better because it can be accessed from any language/toolkit.
For .NET you need a .NET application, with all that implies.
For me that is enough reason to discard it.
.NET is callable from .NET stuff too - you can call a .NET assembly for both
COM (transparently, by just registering the .NET assembly via COMinterop
layer of .NET) and from native code (a bit clumsy, but possible). Also, can
use WebServices stuff and SOAP xml or binary packets (or NEST etc.), or
using .NET Remoting (there are implementations of it in pure Java if I
remember well, similar to how JIntegra implemented DCOM on pure Java). Or
use WinForms and messages (e.g. WM_COPYDATA message on Windows is easy way
to do IPC - have been using it at my Plugs components for VCL and ActiveX -
http://plugs.onestop.net)
But we can discuss about this forever; Our premises are different,
so we cannot ever agree...
indeed, I'll try to rest for a bit and catch up later on to not tire people
with this long discussion
keep on the good work,
George
========================
George Birbilis ([EMAIL PROTECTED])
Microsoft MVP J# 2004-2006
Borland "Spirit of Delphi"
http://www.kagi.com/birbilis
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
