1. News You Can Use
http://news.com.com/2100-1016_3-5150019.html?tag=nefd_top
That's very interesting!
Is it possible to have a client/server system programmed in EUPHORIA?
Like, can a EUPHORIA program function efficiently and effectively as an
app server and/or an app client? I guess, really, that is the smartest
way to go, eh? What say ye, EUPHORIA programmers?
2. Re: News You Can Use
----- Original Message -----
From: "C. K. Lester" <euphoric at cklester.com>
To: <EUforum at topica.com>
Subject: News You Can Use
>
>
> http://news.com.com/2100-1016_3-5150019.html?tag=nefd_top
>
> That's very interesting!
>
> Is it possible to have a client/server system programmed in EUPHORIA?
> Like, can a EUPHORIA program function efficiently and effectively as an
> app server and/or an app client? I guess, really, that is the smartest
> way to go, eh? What say ye, EUPHORIA programmers?
One advantage of smart-client/server systems is that some of the computing work
can be offloaded from the server to the client machine. One of the disadvantages
is that it increases network traffic as a lot more information needs to be moved
between the client and server machines.
These are reversed when using a thin-client or 'dumb'-client (eg. web-browser).
So you need to weigh up what is more appropriate for your application.
--
Derek
3. Re: News You Can Use
Derek Parnell wrote:
>One advantage of smart-client/server systems is that some of the computing work
>can be offloaded from the server to the client machine. One of the disadvantages
>is that it increases network traffic as a lot more information needs to be moved
>between the client and server machines.
>
>
It doesn't seem like that much of an increase in traffic would be
necessary, unless I'm missing something. If you have an app running on a
client PC, it will simply be sending data to the server, and vice versa,
just like in a browser/server app situation now. Where's the "lot more
information?"
4. Re: News You Can Use
Matt Lewis wrote:
>Like Derek said, it depends on your application. Here's an extreme
>example where everything is going on at the client:
>
>
If the server is simply hosting a file, and "everything is going on at
the client," I wouldn't call that a client/server application in any
sense. :)
>...as opposed to a true client-server relationship.
>
And you apparently agree.
>Now suppose that instead, you've got a server somewhere that's running
>an Oracle db, and users have client applications that display forms and
>query the database. The server will do all the heavy processing
>(accessing the database to run queries), and will only transmit the
>results to the clients. The server has to do a lot of work, but you're
>keeping your network traffic as low as possible by only sending what's
>required.
>
>
So between thin-client and thin-server, is there anything useful in
between? I would think so... smart clients and smart servers working
together? Now that's a nice proposition. I see it mainly working for
things like banking, credit card management, etc., where the number of
potential searchable records will remain relatively low (how many
transactions do you do in a year?). And then things like EDI 'n' stuff,
where the user at his PC can prepare the information then connect with
the server at the receiving agency and transmit the data... cha-ching.
At least I'm getting some new ideas and new avenues to take my business!
maybe... :D
