Sorry Finn, I don't completely agree.
DCom in itself is not that easy to poeple not familiar with distributed
objects over a network, moreover to people not familiar with network
programming at all, that's obviously Rob's case. Besides that, DCom is a
hell on earth when it comes to deploy your app on diverse Windows versions
across your network. You need subscribe to MSDN, which is quit expensive,
and its load of monthly CDs to be able to find a way in Microsoft's jungle
of DLL versions all conflicting one with another. Did you know that
installing M$ SBS on Windows NT SP6a {*word*30}s up your DCom registry in a whole
different way than when you have SP4. That sort of thing implies that you
have a strong QA dept. at your service to test over 40 different Windows
versions/configurations to make sure your app still works in each case.
No, DCom is really fine in a controlled homogeneous environment, but you
cannot assume that that's what people always have.
On the other hand I've seen a couple of apps successfully using sockets and
serving 2 or 3 hundreds xml formated request per second.
Rob: there's no harm in using strings (depends on expected server load:
you'll have to profile that) unless you send over the content of entire
books ;)
Cheers to all,
Steph.
--
"I have made this letter longer than usual because I lack
the time to make it shorter." -- Blaise Pascal
"Finn Tolderlund" <f...@nospam.com> a crit dans le message news:
3d0efbaa$1_2@dnews...
Quote
> DCOM comes to mind as a simple way.
> --
> Finn Tolderlund
> "Rob" <ezek...@slingshot.co.nz> wrote in message news:3d0ef4ed_2@dnews...
> > Do you know of a simple way to communicate accross a LAN?