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
|
Not Categorized, Please Help
|
|
