Sync <kdd21@[EMAIL PROTECTED]
> wrote in news:1187822394.192952.85140
@[EMAIL PROTECTED]
> Tried to search for comments on this subject but the Google groups
> search filter on groupname is seriously broken for some reason, it's
> treating "groups:*.progress" just as if the words "groups" and
> "progress" were regular search terms, not a group specification....
>
> At any rate,
>
> Have been working on a script that asynchronously runs a procedure on
> the appserver-- I'm rather new to progress coding, but we need to get
> the two parts to pass data across in the process, and it looked like
> PUBLISH and SUBSCRIBE were just the thing-- however, the server side
> goes thorugh the motions of the publish but the event never fires in
> the client.
>
> I then did a little more poking around on the peg.com forums, and
> found an old comment something to the effect that publish/subscribe
> doesn't work distributed (across sessions), that it was a "wish list
> item." Unfortunately, it's not quite clear to me what the definition
> of a "session" or "distributed" is in that comment-- are the client
> side & server side considered separate sessions in this case and pub/
> sub is therefore unsup****ted? Or am I overlooking something else as
> to the reason the event doesn't fire...
>
> I'm using V9.1d, and using the "run asynchronous on server" technique
> to fire up the appserver end, and using a subscribe with anywhere to
> set up the event handler. I checked the calling parameters, and even
> tried a parameterless pub/sub just in case a parameter mismatch was
> the problem, but no luck.
>
> The main question is-- *should* a subscribe on the client be able to
> get the publish done on the appserver? Or is this in fact not
> implemented? The real unfortunate thing about pub & sub is the
> coupling is so loose there's not much error handling to be had. When
> you "subscribe...anywhere" perhaps the word "anywhere" doesn't really
> *mean* anywhere?...
>
>
> --
>
> Sync
>
>
The process running on th AppServer can't just PUBLISH and expect the
correct client to pick up the message. You'll need Sonic to do a "global"
publish.
However the procedure is quite cabable of returning data back to its
instantiatiing program.
RUN GetNumAccounts.p ON h_Sale***amples
ASYNCHRONOUS SET ghGetNumAccounts
EVENT-PROCEDURE "DisplayNumAccounts"
(INPUT cbSalesRep, OUTPUT NumAccounts AS INTEGER).
Alan
|
