Everything that's old is new again.

It sounds like you want the client-server model of system architecture. Back in the day, this was Very Hot Stuff in the database world. The database functioned as the central server application and many developers wrote client applications that were distributed to the end-users. As long as the whole system did not scale beyond the capabilities of the system managers and developers to maintain, it worked relatively well.

The problems started when the individual applications begin tromping on each other; taking exclusive locks on resources and not releasing them; resetting variables without checking if they are already in use; etc. The issues compounded when it was time for a new release of the client software and you distributed the new client software to many users with a bewildering array of operating systems at various patch levels.

Usually, I saw clients and servers communicating via tcp with remote procedure calls (rpc). If you have any Old Guys around, they probably have linear yards of bookshelf filled with books on the subject.

Good luck

Augie

In reply to Re: What's a good alternative to browser-webapp-webserver for remote apps? by DBAugie
in thread What's a good alternative to browser-webapp-webserver for remote apps? by rudder

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.