>are backing server-side solution which use object-caching (I believe) in one form or
>another. In practice it means that I think we
>are seeing a major split between 100% pure microsoft (SQLServer is the only database
>that will run effectively on their archetecture) and the >rest. And - I'm not sure
>that's to microsoft's advantage.
I agree. There are plenty of companies out there running databases such as Oracle and
DB2. Then if folks use a different operating system, for any number of reasons,
microsoft solutions become useless. (Why use solutions that can function only in part
of a company's infrastructure?)
>>> Robert Burrell Donkin <[EMAIL PROTECTED]> 10/11/2000 4:59:07 PM >>>
Mark Mynsted wrote:
> > For those who don't know about microsoft's web application archetecture, it uses
> > extensive client-side processing.
> > The microsoft standard archetecture seems to want to use COM to implement it's data
> > access. Quite how this will ever work robustly either on a large network or on a
> > non-winX machine I don't know.
>
> Microsoft's entire mission seems to be to build programming practices around making
>it impossible to deploy applications to machines without Microsoft software, and to
>get as many people developing software this way as possible. Good for them, but I do
>not buy in to it.
>
> It seems like there is a right way and a Microsoft way to do everything.
>
Sometimes the microsoft verses the world thingy gets in the way of more fundemental
questions about how http mediated applications should work. The microsoft MTS approach
is actually much more like functional programming (remember that?) - *but* without
telling anybody what
it is and using totally inappropriate langauges (which is a shame, since as a friend
of mine insists on telling me, microsoft have invested a large amount of money into
reasonable open-source language projects in this area) - plus of course ensuring that
it will only run on
microsoft platforms. I read that there has been a major fallout amongst the design
generals about this general approach. Sort of everybody else are backing server-side
solution which use object-caching (I believe) in one form or another. In practice it
means that I think we
are seeing a major split between 100% pure microsoft (SQLServer is the only database
that will run effectively on their archetecture) and the rest. And - I'm not sure
that's to microsoft's advantage.
robert
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]