API_Rules - iMaxsoft

makeshiftklipInternet και Εφαρμογές Web

31 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

87 εμφανίσεις



www.Abovehealth.Com




2085 Hamilton Ave., San Jose, CA 95125


Page:
1


AIM auto
-
detect feature for Persistent and Standby, enhanced
ltexec():


SERVER:



LISTENER Initiation and SERVER Program API:



-
program_name

-

the prefix

-


in front of server program name is the hint to
LISTENER to initiate the server program in PERSIS
TENT mode;
the corresponding client call is

lt_msg_enter_clt_async_(), lt_msg
_enter_clt (), and lt_msg_enter_clt_()
, the program_name parameter
should contain the same prefix

-





+
program_name

-

the prefix
‘+‘

in front of server program name is the hi
nt to
LISTENER to initiate the server program in STANDBY mode; the
corresponding client call
is lt_msg_enter_clt_async_(), lt_msg
_enter_clt (), and lt_msg_enter_clt_()
, the program_name parameter
should contain the same prefix
‘+‘



lt_msg_is_standby()

-

new API for server program to determine whether itself is in
PERSISTENT (return=0) mode or STANDBY (return<>0) mode; the
environment variables for PERSISTENT/STANDBY are no longer
used,
they should not be used
.



AIM enhanced API

-

lt_msg_enter_(), lt_msg
_send_(), lt_msg_recv_() for server, and
lt_msg_enter_clt_async_(), lt_msg_send_clt_(), lt_msg_recv_clt_()
for client and make sure when lt_msg_enter_clt_async_() is being
used, appropriate
+/
-
program_name must be specified to in
-
sync with
server PERSISTEN
T/STANDBY mode.




CLIENT:



ltexec_

-

this client routine internally calls lt_msg_enter_clt_async_() and
uses predix
‘+’
for

program_name as the program name (STANDBY
mode)



ltexecp_

-

this client routine internally calls lt_msg_enter_clt_async_() and

uses prefix

-

for

program_name as the program name
(PERSISTENTmode)



ltexec0_

-

this client routine internally calls lt_msg_enter_clt_async_() and
uses predix
‘+’
for

program_name as the program name (STANDBY
mode)


ltexec0

-

ltexec0 and ltexec0 sup
port additional parameters (host_name,
port_number, … etc.,)


CLIENT

SERVER

lt_msg_enter_clt

lt_msg_enter, lt_msg_enter_

lt_msg_enter_clt_

lt_msg_enter, lt_msg_enter_

lt_msg_enter_clt_async_

lt_msg_enter, lt_msg_enter_



lt_msg_send_clt, lt_msg_send_c
lt_

lt_msg_send, lt_msg_send_



www.Abovehealth.Com




2085 Hamilton Ave., San Jose, CA 95125


Page:
2

lt_msg_recv_clt, lt_msg_recv_clt_

lt_msg_recv, lt_msg_recv_



lt_msg_leave_clt

lt_msg_leave


lt_msg_enter* drives the server program launching mode via server listener:



case 1:

if server program is pre
-
launched in standb
y mode via server listener;


if +program_name is used from the client, then the pre
-
launched standby program will be
used,

if +program_name has no match to the pre
-
launched standby program, then error will be
returned



case 2:

if
-
program_name is used fro
m the client, then the server listener will launch the server
program in persistent mode regardless whether there is matching server program in
standby mode or not



case 3:

if server program is pre
-
launched in standby mode via server listener;


if program
_name is used from the client, then the pre
-
launched standby program will be
used first,

if program_name has no match to the pre
-
launched standby program, then the server
listener will launch the server program in persistent mode



TRHEAD:



ltexec0 and lt
exec0_

-

is thread
-
safe, for application server that uses lt_msg_enter_, the web
server program should use ltexec0_.


ltexecp_

-

is
not

thread
-
safe and it supports only one connection internally, so
each client .exe can only have one set of host, port, pro
gram
configuration per ltexecp_.


ltexec_

-

is thread
-
safe and can have multiple concurrent connections for a
client .exe.



ltxtx

-

is
not

thread
-
safe, this is the API to replace all ltexec* and ltexecp*,
this is a standardized API for LeeTech internal u
se only. It should not
be used for web application (not thread
-
safe), it is used for client
with single 3
-
tier connection .exe, it detects program name prefix, if
is +, then the standby mode is expected, otherwise the persistent
mode is used.



www.Abovehealth.Com




2085 Hamilton Ave., San Jose, CA 95125


Page:
3

AIM In
-
house

Standard as of 7/17/2000:


Standard 3
-
tier Internal API:



ltexec0_()

-

this client routine internally calls lt_msg_enter_clt_async_() and
uses predix
‘+’
for

program_name as the program name (STANDBY
mode)


for all WEB application development


ltxtx()

-

is
not

thread
-
safe, this is the API to replace all ltexec* and ltexecp*,
this is a standardized API for LeeTech internal use only. It should not
be used for web application (not thread
-
safe), it is used for client
with single 3
-
tier connection .exe, it
detects program name prefix, if
is +, then the standby mode is expected, otherwise the persistent
mode is used


for CLIENT/SERVER application development



lt_msg_is_standby()

-

new API for server program to determine whether itself is in
PERSISTENT (retu
rn= 0 or FALSE) mode or STANDBY
(return<>0 or TRUE) mode; the environment variables for
PERSISTENT/STANDBY are no longer needed,
they should not be
used
.



CLIENT

SERVER

lt_msg_enter_clt

lt_msg_enter

lt_msg_enter_clt_async_

lt_msg_enter_



lt_msg_send_
clt

lt_msg_send

lt_msg_recv_clt

lt_msg_recv

lt_msg_send_clt_

lt_msg_send_

lt_msg_recv_clt_

lt_msg_recv_



lt_msg_leave_clt

lt_msg_leave




TRHEAD:



ltexec0_

-

is thread
-
safe, for application server that uses lt_msg_enter_, the web
server program sho
uld use ltexec0_.


ltxtx

-

is
not

thread
-
safe, this is the API to replace all ltexec* and ltexecp*,
this is a standardized API for LeeTech internal use only. It should not
be used for web application (not thread
-
safe), it is used for client
with single 3
-
t
ier connection .exe, it detects program name prefix, if
is +, then the standby mode is expected, otherwise the persistent
mode is used.