by BeeJay >> Tue, 10 Aug 1999 23:06:53 GMT
I'll make an assumption here that you simply want to have a server app that waits for notifications, processes them to completion and once it's started processing a notification you don't want to interrupt this processing to allow another notification to be received. If I wanted to allow "smaller" notification processing to interleave with "long" notification processing then I would probably simplify my coding by creating a second server app that processes only the "long running" notifications.
1) Define a new app in the application browser as appropriate for a server application:
ie: With initialise/finalise methods and no startup form.
2) Ensure you've added the appropriate ServerApplicationX = <schema>,<app> in your ini file.
3) In your initialise method setup the appropriate notifications withbegin Notification or beginClassNotification.
4) In your finalise method use endNotification and endClassNotification as appropriate for those notifications that were setup in the initialise method.
5) Create your sysNotification and userNotification methods to handle the notifications as appropriate for your application requirements.
Now, assuming you've coded your initialise method to complete sometime after it has setup the notifications your server application will now be waiting in an idle state for a notification to arrive. When one arrives, the sys/user notification method will execute as appropriate and assuming you've also coded these to complete your server application will go back into an idle state once it's finished processing the notification ready for the next notification.
Hope this helps.
Cheers,
BeeJay.