Re: Web listener
- From: Kevin Powick <kpowick@xxxxxxxxx>
- Date: Sun, 14 Dec 2008 17:46:32 -0800 (PST)
On Dec 14, 6:00 pm, "Peter McMurray" <excalibu...@xxxxxxxxxxx> wrote:
Up until now D3 on Microsoft has been my weapon of
choice. However the failure to address Vista and 2008 make me look at other
options.
Then run D3 on Linux. Windows/Linux shouldn't make any difference to
the possible middle tier technologies you've mentioned. I'm not a big
D3 fan, it's just that if you know it well, you may wish to stick
with it.
QM is very attractive especially as I have a
truck computer project on the go- those O'Neill printers really turn me on
:-) I love Land Rovers but towing a printer behind one and then printing
from it is awesome.
I like QM, but I really don't understand the rest of your comment.
we had a laptop go under a log skidder the other day, it did not survive.
However QM with a pda and a mobile phone is an ace setup.
Are you talking about the PDA version of QM? That's neither a client
nor server set-up. It's a single user, stand-alone version that would
have little to do with multi-tier system architecture.
Plus the users
are extremely adept at uploading and downloading stuff to their phones.
Except that downloading "stuff" is not bi-directional, nor even close
to real-time, interactive communication with a remote application.
What I would like to do is an MV agnostic platform that produces
DHTML/Javascript pages from my parameter based methods.
I want it to work
in Linux as well as Microsoft. The client side is fine, the MV side is
fine, I am now just battling with the middle ware.
In this case, part of your middle tier will be a web server capable of
supporting the operating systems and development tools you wish to
use. This actually isn't that hard, as there are many available. The
standard IIS and Apache may be fine, but here is a list of
alternatives.
http://www.debianhelp.co.uk/apachealternatives.htm
So I am getting a great deal from this thread and hunting up
all sorts of stuff from PHP on, however MVWWW and the sockets from Bryan et
al is getting a lot of thought.
Whatever your choice, I would stay away from trying to serve up web
content directly from the MV side of things. Too messy. Your web
server app should be talking to your middleware to get the required
data for the content you push to the client browser.
Browser <--> Webserver <--> Middleware <--> MV
Desktop App <--> Middleware <--> MV
PDA/iPhone <--> Middleware <--> MV
Notice there are no "connections" that bypass any components. In all
of the above cases, the Middleware and MV components should not
require ANY changes. Of course, you have to decide on a transport and
data format that would allow you to do this. We've chosen XML
structures over HTTP.
Peter, if I get some time, I'll put up a demo you can download to
better see what I've attempted to describe.
--
Kevin Powick
.
- Follow-Ups:
- Re: Web listener
- From: Peter McMurray
- Re: Web listener
- References:
- Web listener
- From: Peter McMurray
- Re: Web listener
- From: Kevin Powick
- Re: Web listener
- From: Peter McMurray
- Re: Web listener
- From: Kevin Powick
- Re: Web listener
- From: Peter McMurray
- Web listener
- Prev by Date: Re: Web listener
- Next by Date: Re: Joulukadun avajaiset Raahessa 28112008015.mp4 [154/324]
- Previous by thread: Re: Web listener
- Next by thread: Re: Web listener
- Index(es):
Relevant Pages
|