[
Lists Home |
Date Index |
Thread Index
]
I'm not asking so much about big applications delivered via a
webcentric model, I know there are many, indeed the argument of having
a non-web client seems extremely old fashioned. What I'm wondering
about is specifically browser based applications running either on an
intranet or on an individual machine accessable over another port than
80.
The idea Lucas Gonze had to base the application in Firefox might also
be a reasonable one.
I wonder how many examples there are of that. How cross-platform would
such a customized version be, any chance of platform inconsistencies
creeping in, and if so how to defend against it
On 2/6/06, Rick Marshall <rjm@zenucom.com> wrote:
> we don't use java (we have other technologies) but we deliver all our
> applications this way. and they are big.
>
> one is a manufacturing planning, control, costing, order entry etc. it
> is web based because it is in use by staff moving around the world
> (particularly, but not only, china and australia). it's also used as the
> access point for the factory to complete manufacturing data and access
> packing lists etc.
>
> xml moves data between servers - the warehouse oeprates from independent
> machines
>
> another is a large retail management application - rented on our servers
> by many customers. and then there's distribution.
>
> this is technology that has been viable for 10 years now and we wouldn't
> plan a project any other way.
>
> having said that, you need a compliant database (and i still don't
> think, in spite of it's popularity, that sql based stuff is the answer),
> you need to use javascript, css, xml, etc and it doesn't come in nice
> developer centers. but it works so well.
>
> the only argument against it is the number of technologies programming
> staff need to be skilled at. (or if you must use java, the complexity of
> it all).
>
> everything else is good.
>
> rick
>
> bryan rasmussen wrote:
>
> >Hi,
> >I'm in the start up phase of a project that should provide a gui
> >client as one of its deliverables. I argued today for a browser based
> >client, because there was frankly nothing I could see that meant it
> >should not be in the browser, the other argument was that it would be
> >java based because it was required to be cross-platform (which I
> >pointed out one could expect the browser based client to be as well)
> >
> >Another argument I put forward would be that we could produce it as a
> >web based client that would be accessable at either an url or as a web
> >based client that people could download and install and run as
> >localhost on a different port than 80.
> >
> >There are numerous programmer tools that use this strategy, for
> >example various databases but I'm aware of only two end user
> >applications of any major size that have used this approach, the open
> >source erlang-based J-EAI and Google Desktop . Does anyone know of any
> >others? Can anyone make any arguments against this particular model
> >for local clients, arguments for?
> >
> >-----------------------------------------------------------------
> >The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> >initiative of OASIS <http://www.oasis-open.org>
> >
> >The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> >To subscribe or unsubscribe from this list use the subscription
> >manager: <http://www.oasis-open.org/mlmanage/index.php>
> >
> >
> >
> >!DSPAM:43e7a4e197751801011259!
> >
> >
> >
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
>
|
