GregTomkins
Active Member
We expose several of our .p's as Java proxies in the following style:
I think I am aware of all the plusses and minuses of doing it this way (I thought about enumerating them here, but decided it would make this post overly tedious).
My question is whether this style is typical or whether people tend to just proxy the 'real_work.p' style procedures directly? Any other comments on how people go about exposing .p's through proxies?
EDIT: added code tags in the hopes Stefan might read this.
Code:
/* real_work.p - known only to us, the vendor of the application */
DEF INPUT PARAM p_account AS CHAR. /* etc. etc. */
/* a ton of real work goes here, RUN, FIND, FOR EACH etc. */
/* proxy.p - known to Java users, our customers; proxied using ProxyGen */
PROCEDURE do_real_work:
DEF INPUT PARAM p_account AS CHAR NO-UNDO.
/* Generally and ideally, there is little to no additional code here */
RUN real_work.p(p_account).
END.
I think I am aware of all the plusses and minuses of doing it this way (I thought about enumerating them here, but decided it would make this post overly tedious).
My question is whether this style is typical or whether people tend to just proxy the 'real_work.p' style procedures directly? Any other comments on how people go about exposing .p's through proxies?
EDIT: added code tags in the hopes Stefan might read this.