Announcement

Collapse

PM and other Problems

We seem to be experiencing system-wide problems with Personal Messages, Notifications, and other secondary systems. Our Forum Hosting company has been alerted. This DOES affect the ability of Admins to respond to outstanding PMs, forum-access requests, and other items as well; please be patient.
See more
See less

Events documentation

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Events documentation

    I don't understand this bit of the documentation about EVENTS:

    One or more clients may choose to "subscribe" to events from a server object by executing the EVENTS FROM statement. The subscription is terminated by execution of the EVENTS END statement. When the server executes RAISEEVENT or OBJECT RAISEEVENT, all clients which have unsubscribed to these events are called. PowerBASIC servers support up to 32 concurrent client subscribers per server object.
    unsubscribed?

  • #2
    Haven't read it, but can't help but believe its a typo.
    Fred
    "fharris"+Chr$(64)+"evenlink"+Chr$(46)+"com"

    Comment


    • #3
      Subscription = EVENTS FROM oMath CALL oStatus
      Cancel subscription = EVENTS END oStatus

      See Event Source in the Docs.

      Edit: Might be useful to look at differently.

      One object uses RAISEEVENT to send a notice. Who gets that notice? Everyone that issued an EVENTS FROM ..., at least until they issue an EVENTS END.

      Reedit: Also from the docs "32 concurrent client subscribers ". I.e. EVENTS FROM could be issued for up to 32 different objects. If 32 objects had an EVENTS FROM issued for them, when the server issued a raise event, it would send the event to all 32 objects (the subscribers). Think of a newspaper or magazine subscription, very, very similar.
      Last edited by Larry Charlton; 20 Mar 2012, 01:44 PM.
      LarryC
      Website
      Sometimes life's a dream, sometimes it's a scream

      Comment

      Working...
      X