Par2: Using the "linked in" broker 1999-11-03 -- Jim DeFabia One aspect of the linked-in App Server (broker) that might not be obvious is
that it
allows you to create and distribute web-enabled apps that users can run on
their desktops and see in their browsers.
This allows you to distribute or email an EXE and its associated files to a
client or potential client for demo purposes. The client does not need
Clarion or the App Server (broker) installed.
Here are the steps to distribute:
1) ship your EXE, its required DLLs and its related data files and any other
external files it needs. Typically this list will be:
yourapp.exe
Your data files
c55runx.dll
c55ascx.dll
c55dosx.dll
c55tpsx.dll (or the file driver you chose for your data files)
c55layx.dll
c55ibcx.dll
skeleton.dll
C55brem.dll
PLUS
the entire skeleton directory and its contents.
the images you need (e.e., x.gif ) in a public directory.
deploy to a dir structure like this:
x:---
|--appdir
|----skeleton
|----public
where appdir contains the files listed above and the skeleton dir contains
all your skeletons and the public folder contains the images you need.
You will find all of these conveniently located in your \distrib folder.
Now the user can double-click on the EXE and the app runs in the local
browser. (NB: requires TCP/IP and a Browser be installed on the client
machine, but most of today's machines already have this).
As for "real" deployment over the Web... Sorry. The linked-in App Server
(broker) always uses 127.0.0.1 (localhost) so it is limited to local use.
Printed May 4, 2024, 1:05 pm This article has been viewed/printed 35114 times. |