🚀 go-pugleaf

Hello,
I would appreciate it if anyone can send me a FAQ for this technology, or
make some reading recommendations for the general topic of client/server.
It's been a buzz-word to me for quite a while, and I think I understand
it sometimes and then I don't.

It's kind of confusing when you toss in distributed computing, too.
For example, we're developing an application that's considered by the
people who designed it to be client/server based (I don't necessary dispute
it, I just don't know).  We have a unix database server, and a IBM PC
acting as the client.  The part in question is how we're updating
changes to the database.  We query the database and get result sets
back, let the user manipulate these result sets, and then send the result
sets back to the unix machine, where a process "walks" the result set and
updates the database accordingly (ie inserts new records, updates
changed records, deletes records marked to be deleted).  In this way, we
are able to enforce "business rules" for business data relationship
integrity (ie any credits from any account must correspond to a debit
elsewhere) on the server.  But it seems to me like the server has too
much of the application's logic embedded in it.

Is this a correct way to apply the client-server approach?  Is this a
good way to apply it?  Are there other ways?

Replies via e-mail greatly appreciated.

Thanks,
d/wang
-- 
--------------------------------------------------------------------------------
Dontin Wang
dwang@nis.naitc.com
--------------------------------------------------------------------------------