Event Service Avatar
  1. OMG Specification

Event Service — All Issues

  • Acronym: EVNT
  • Issues Count: 5
  • Description: All Issues
Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
EVNT11-12 Clarification needed for "at least one consumer" clause EVNT 1.0b1 EVNT 1.0 Resolved closed
EVNT11-9 Creation of ProxyPushSupplier interfaces EVNT 1.0b1 EVNT 1.0 Resolved closed
EVNT11-8 Key type definition EVNT 1.0b1 EVNT 1.0 Resolved closed
EVNT11-11 connect_* operations in sections 4.5.(4,5,6,7) EVNT 1.0b1 EVNT 1.0 Resolved closed
EVNT11-10 Disconnected exception EVNT 1.0b1 EVNT 1.0 Resolved closed

Issues Descriptions

Clarification needed for "at least one consumer" clause

  • Key: EVNT11-12
  • Legacy Issue Number: 640
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 4.4.4, p.4-13 last sentence:If channel responsible for pulling incoming events, then it will issue a request to get event.Or does it mean that event channel will not try to get event
  • Reported: EVNT 1.0b1 — Wed, 30 Jul 1997 04:00 GMT
  • Disposition: Resolved — EVNT 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Sun, 8 Mar 2015 19:23 GMT

Creation of ProxyPushSupplier interfaces

  • Key: EVNT11-9
  • Legacy Issue Number: 25
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is it implied that obtain_push_supplier causes the creation/allocation of a ProxyPushSupplier interface?
  • Reported: EVNT 1.0b1 — Mon, 1 Jul 1996 04:00 GMT
  • Disposition: Resolved — EVNT 1.0
  • Disposition Summary:

    Rejected
  • Updated: Sun, 8 Mar 2015 19:23 GMT

Key type definition

  • Key: EVNT11-8
  • Legacy Issue Number: 17
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: TypedConsumerAdmin and TypedSupplierAdmin have operations that take a "Key" type (which identifies an interface), but do not specify the specific value needed to ID an interface.
  • Reported: EVNT 1.0b1 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Resolved — EVNT 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Sun, 8 Mar 2015 19:23 GMT

connect_* operations in sections 4.5.(4,5,6,7)

  • Key: EVNT11-11
  • Legacy Issue Number: 633
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The connect_* operations in these sections raise an AlreadyConnected exception if the client is already connected!? In some cases the channel will allow consumer to connect twice
  • Reported: EVNT 1.0b1 — Thu, 24 Jul 1997 04:00 GMT
  • Disposition: Resolved — EVNT 1.0
  • Disposition Summary:

    Rejected
  • Updated: Sun, 8 Mar 2015 19:23 GMT

Disconnected exception

  • Key: EVNT11-10
  • Legacy Issue Number: 93
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The conditions for raising the Disconnected exception are not consistent with the state diagram on page 4-14.
  • Reported: EVNT 1.0b1 — Wed, 28 Aug 1996 04:00 GMT
  • Disposition: Resolved — EVNT 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Sun, 8 Mar 2015 19:23 GMT