From dpg1@grisby.org Mon May 27 10:35:57 2002 Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g4R9Zvu00825 for ; Mon, 27 May 2002 10:35:57 +0100 Received: from pc1-camc4-0-cust148.cam.cable.ntl.com ([80.2.246.148]) by mta03-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020527093559.GFKL295.mta03-svc.ntlworld.com@pc1-camc4-0-cust148.cam.cable.ntl.com> for ; Mon, 27 May 2002 10:35:59 +0100 Received: from grisby.org (dpg1@localhost) by pc1-camc4-0-cust148.cam.cable.ntl.com (8.11.2/8.11.2) with ESMTP id g4R9Zwi23825 for ; Mon, 27 May 2002 10:35:58 +0100 Message-Id: <200205270935.g4R9Zwi23825@pc1-camc4-0-cust148.cam.cable.ntl.com> X-Authentication-Warning: pc1-camc4-0-cust148.cam.cable.ntl.com: dpg1 owned process doing -bs To: omninotify-list@realvnc.com From: Duncan Grisby Subject: [omniNotify] omniNotify mailing list's new home Sender: omninotify-list-admin@realvnc.com Errors-To: omninotify-list-admin@realvnc.com X-BeenThere: omninotify-list@realvnc.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon May 27 10:38:01 2002 X-Original-Date: Mon, 27 May 2002 10:35:58 +0100 Hi, As some of you have already noticed, the omniNotify mailing list has a new home, courtesy of realvnc.com. The plan to host it at the Cambridge University Engineering department didn't work out, so our VNC friends are helping out. With any luck, we'll manage to get back control of the omniorb.org domain, at which point the list address can revert to @omniorb.org. The list is now run with Mailman rather than Majordomo, so the subscription interface is different. You can control your membership through this web page: http://www.realvnc.com/mailman/listinfo/omninotify-list To modify your settings, you need to know your password, which of course you won't. To find out what it is, go to that page and type your email address in to the box at the bottom. Click on "Edit Option", and you'll get to a page that includes an option to have your password emailed to you. If you have any problems let me know. Unfortunately, due to a slight mishap, we lost the mailing list archives. If anyone happens to have a reasonably complete copy of the mailing list archive, please let me know. Cheers, Duncan. -- -- Duncan Grisby -- -- duncan@grisby.org -- -- http://www.grisby.org -- From tvedt@noao.edu Mon Jul 15 20:54:11 2002 Received: from noao.edu (email.tuc.noao.edu [140.252.1.54]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g6FJs8T09522 for ; Mon, 15 Jul 2002 20:54:09 +0100 Received: from pertelote.tuc.noao.edu ([140.252.38.2] verified) by noao.edu (CommuniGate Pro SMTP 3.5.9) with ESMTP id 4719931 for omninotify-list@realvnc.com; Mon, 15 Jul 2002 12:54:05 -0700 Received: from pertelote.tuc.noao.edu (pertelote.tuc.noao.edu [140.252.38.2]) by pertelote.tuc.noao.edu (8.9.1/8.9.1/SAG-04Feb01) with SMTP id MAA26785 for ; Mon, 15 Jul 2002 12:54:05 -0700 (MST) Message-Id: <200207151954.MAA26785@pertelote.tuc.noao.edu> From: Janet Tvedt Reply-To: Janet Tvedt To: omninotify-list@realvnc.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: wQwiBA06DfrZkBheHE4Xtw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc Subject: [omniNotify] performance questions Sender: omninotify-list-admin@realvnc.com Errors-To: omninotify-list-admin@realvnc.com X-BeenThere: omninotify-list@realvnc.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Jul 15 22:14:24 2002 X-Original-Date: Mon, 15 Jul 2002 12:54:05 -0700 (MST) From the documentation it appears that omniNotify does honor priority and timeout values for events that it receives. Is this true? Also, is there an easy way to support a "pull event period" of "on demand"? I have not tried using pull functionality with omniNotify because it was distastrous with the event service implementations I tried. In some cases (well, in my world anyway) a pull consumer may require an update once or twice in its lifetime, so continuous polling is overkill. Any ideas? Thanks! Janet -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 From gruber@research.att.com Mon Jul 15 23:23:53 2002 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g6FMNqT16708 for ; Mon, 15 Jul 2002 23:23:52 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id 8A6CF4CE78; Mon, 15 Jul 2002 18:23:51 -0400 (EDT) Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.8.8/8.8.8) with SMTP id SAA26071; Mon, 15 Jul 2002 18:23:51 -0400 (EDT) From: "Robert E. Gruber" To: "Janet Tvedt" , Cc: "Robert E. Gruber" Subject: RE: [omniNotify] performance questions Message-ID: <007201c22c4e$34639d50$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <200207151954.MAA26785@pertelote.tuc.noao.edu> Sender: omninotify-list-admin@realvnc.com Errors-To: omninotify-list-admin@realvnc.com X-BeenThere: omninotify-list@realvnc.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Jul 15 23:24:01 2002 X-Original-Date: Mon, 15 Jul 2002 18:23:11 -0400 > From the documentation it appears that omniNotify does honor priority and > timeout values for events that it receives. Is this true? Yes, omniNotify supports OrderPolicy and DiscardPolicy, and the settings of PriorityOrder and DeadlineOrder are used to indicate control based on Priority or Timeout values, respectively. omniNotify applies these policies at the level of individual consumer queues; it does not support a DiscardPolicy based on Priority or Timeout at the global incoming event queue. OrderPolicy is only relevant if the channel has more than one event queued up for a given consumer. This happens for both push and pull batch consumers, and also for single-event pull consumers. For single-event push consumers, the queue size is normally 1 or 0 because events are pushed out of the queue immediately after they are added, so OrderPolicy does not have any effect. DiscardPolicy is only relevant if MaxEventsPerConsumer is set to positive value K, and K+1 events have been queued up for a given consumer. In this case, DiscardPolicy controls which of the K+1 events is discarded to return the queue size to K. > Also, is there an easy way to support a "pull event period" of "on demand"? > I have not tried using pull functionality with omniNotify because it was > distastrous with the event service implementations I tried. In some cases > (well, in my world anyway) a pull consumer may require an update once or > twice in its lifetime, so continuous polling is overkill. Any ideas? I'm not sure what you are asking for. PullEventPeriod applies to pull suppliers, and it is a millisecond-based control. Are you saying that instead of, say, pulling every 100 milliseconds, an "on-demand" pull supplier would only be polled by the channel if a pull-style consumer did a pull or try_pull call? One way to implement something like this without changing omniNotify is to use push suppliers/consumers and to have an extra event type that is used to request an event push. E.g., have event type SomeDomain::Foo for foo events, and use SomeDomain::NeedFoo to signal that a Foo event is needed. A push consumer could register for Foo events, and could push a NeedFoo event to the channel when it needs a Foo event. A push supplier could register as a consumer of NeedFoo events, and for each one it receives, it would push a Foo event to the channel. If I did not understand what you need, please send more details. -- Bob -----Original Message----- From: omninotify-list-admin@realvnc.com [mailto:omninotify-list-admin@realvnc.com]On Behalf Of Janet Tvedt Sent: Monday, July 15, 2002 3:54 PM To: omninotify-list@realvnc.com Subject: [omniNotify] performance questions From the documentation it appears that omniNotify does honor priority and timeout values for events that it receives. Is this true? Also, is there an easy way to support a "pull event period" of "on demand"? I have not tried using pull functionality with omniNotify because it was distastrous with the event service implementations I tried. In some cases (well, in my world anyway) a pull consumer may require an update once or twice in its lifetime, so continuous polling is overkill. Any ideas? Thanks! Janet -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 _______________________________________________ omninotify-list mailing list omninotify-list@realvnc.com http://www.realvnc.com/mailman/listinfo/omninotify-list From tvedt@noao.edu Thu Sep 5 00:12:23 2002 Received: from realvnc.com ([213.239.45.162]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g84NCN816325 for ; Thu, 5 Sep 2002 00:12:23 +0100 Received: from noao.edu (noao.edu [140.252.1.54]) by realvnc.com (8.11.6/8.11.6) with ESMTP id g84NDKx04700 for ; Thu, 5 Sep 2002 00:13:20 +0100 Received: from pertelote.tuc.noao.edu ([140.252.38.2] verified) by noao.edu (CommuniGate Pro SMTP 4.0b7) with ESMTP id 5154382 for omninotify-list@realvnc.com; Wed, 04 Sep 2002 16:12:25 -0700 Received: from pertelote.tuc.noao.edu (pertelote.tuc.noao.edu [140.252.38.2]) by pertelote.tuc.noao.edu (8.9.1/8.9.1/SAG-04Feb01) with SMTP id QAA05887 for ; Wed, 4 Sep 2002 16:12:25 -0700 (MST) Message-Id: <200209042312.QAA05887@pertelote.tuc.noao.edu> From: Janet Tvedt Reply-To: Janet Tvedt To: omninotify-list@realvnc.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: ULSya4AYSZCXOpF3ThEyZw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc Subject: [omniNotify] obtain_offered_types Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Sep 5 00:13:00 2002 X-Original-Date: Wed, 4 Sep 2002 16:12:24 -0700 (MST) Is obtain_offered_types() in the following interface supported by omniNotify? It doesn't appear to return anything, although obtain_subscription_types() does. interface EventChannel : CosNotifyChannelAdmin::EventChannel { CosNotification::EventTypeSeq obtain_subscription_types(); CosNotification::EventTypeSeq obtain_offered_types(); ... } -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 From gruber@research.att.com Thu Sep 5 14:50:35 2002 Received: from realvnc.com ([213.239.45.162]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g85DoZ821076 for ; Thu, 5 Sep 2002 14:50:35 +0100 Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by realvnc.com (8.11.6/8.11.6) with ESMTP id g85DpWx09737 for ; Thu, 5 Sep 2002 14:51:32 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id DC1F74CE29; Thu, 5 Sep 2002 09:50:31 -0400 (EDT) Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.8.8/8.8.8) with SMTP id JAA09629; Thu, 5 Sep 2002 09:50:30 -0400 (EDT) From: "Robert E. Gruber" To: "Janet Tvedt" , Cc: "Robert E. Gruber" Subject: RE: [omniNotify] obtain_offered_types Message-ID: <000001c254e2$fc1ac4b0$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal In-reply-to: <200209042312.QAA05887@pertelote.tuc.noao.edu> Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Sep 5 14:51:02 2002 X-Original-Date: Thu, 5 Sep 2002 09:48:58 -0400 obtain_offered_types returns the types that have been 'offered' by one or more suppliers using the offer_change method. If no suppliers have invoked offer_change with a list of types that they supply, then obtain_offered_types will not return anything. Suppliers can supply events of arbitrary type without 'offering' them first, so many users of the notification service do not bother to use the offer_change mechanism. In fact, I'm curious: is anybody using it? The AttN::EventChannel interface has the function you mentioned for admin/monitoring purposes, as a a one-time get of the current offered types set. A consumer that wants to know about offered types should use the proxy-level obtain_offered_types call, which has this signature: CosN::EventTypeSeq* obtain_offered_types(CosNA::ObtainInfoMode mode) The mode indicates 2 things: whether this is actually a request for the offered types, and whether the consumer wishes to be informed of future changes to the set of offered types. Thus the four modes are: CosNA::NONE_NOW_UPDATES_OFF : do not return current offered types, and do not send future offer_change updates CosNA::NONE_NOW_UPDATES_ON : do not return current offered types, but send future offer_change updates CosNA::ALL_NOW_UPDATES_OFF : send current offered types, but do not send future offer_change updates CosNA::ALL_NOW_UPDATES_ON : send current offered types, and send future offer_change updates A bit of a warning: due to the asynchronous nature of the service, using offer_change messages to control consumer interest can be a bit tricky. For example, if a supplier announces a new event type T using offer_change, and then immediately starts supplying T events, by the time a consumer learns of the type T offer and adds a subscription for it, some of the newly announced T events may already have been processed by the channel. If the intent was that the consumer should get all T events, then either the consumer should always be registered for T events, or the supplier needs to wait for a 'reasonable' amount of time before it starts to supply T events. -- Bob -----Original Message----- From: omninotify-list-admin@omniorb-support.com [mailto:omninotify-list-admin@omniorb-support.com]On Behalf Of Janet Tvedt Sent: Wednesday, September 04, 2002 7:12 PM To: omninotify-list@realvnc.com Subject: [omniNotify] obtain_offered_types Is obtain_offered_types() in the following interface supported by omniNotify? It doesn't appear to return anything, although obtain_subscription_types() does. interface EventChannel : CosNotifyChannelAdmin::EventChannel { CosNotification::EventTypeSeq obtain_subscription_types(); CosNotification::EventTypeSeq obtain_offered_types(); ... } -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 _______________________________________________ omninotify-list mailing list omninotify-list@omniorb-support.com http://www.omniorb-support.com/mailman/listinfo/omninotify-list From tvedt@noao.edu Sat Oct 5 01:36:26 2002 Received: from realvnc.com ([213.239.45.162]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g950aQ805263 for ; Sat, 5 Oct 2002 01:36:26 +0100 Received: from noao.edu (email.tuc.noao.edu [140.252.1.54]) by realvnc.com (8.11.6/8.11.6) with ESMTP id g950cA510831 for ; Sat, 5 Oct 2002 01:38:10 +0100 Received: from pertelote.tuc.noao.edu ([140.252.38.2] verified) by noao.edu (CommuniGate Pro SMTP 4.0b8) with ESMTP id 5438306 for omninotify-list@realvnc.com; Fri, 04 Oct 2002 17:36:18 -0700 Received: from pertelote.tuc.noao.edu (pertelote.tuc.noao.edu [140.252.38.2]) by pertelote.tuc.noao.edu (8.9.1/8.9.1/SAG-04Feb01) with SMTP id RAA12117 for ; Fri, 4 Oct 2002 17:36:08 -0700 (MST) Message-Id: <200210050036.RAA12117@pertelote.tuc.noao.edu> From: Janet Tvedt Reply-To: Janet Tvedt To: omninotify-list@realvnc.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 9U95RKWGGuwtQRiC7dxZBg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc Subject: [omniNotify] org.omg.CosNotifyComm.InvalidEventType Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Sat Oct 5 01:37:00 2002 X-Original-Date: Fri, 4 Oct 2002 17:36:08 -0700 (MST) I am getting an org.omg.CosNotifyComm.InvalidEventType exception when a StructuredPushSupplier calls offer_change with an EventType("foo.bar", "baz"). However, EventType("foo", "baz") works fine. This dotted naming scheme is working fine for sending/receiving structured events, even with filters. So I am puzzled as to why it doesn't work in this context. Any ideas? -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 From gruber@research.att.com Mon Oct 7 18:03:26 2002 Received: from realvnc.com ([213.239.45.162]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g97H3P808401 for ; Mon, 7 Oct 2002 18:03:26 +0100 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by realvnc.com (8.11.6/8.11.6) with ESMTP id g97H5N507490 for ; Mon, 7 Oct 2002 18:05:23 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id AEC194CE6F; Mon, 7 Oct 2002 13:03:20 -0400 (EDT) Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.8.8/8.8.8) with SMTP id NAA23116; Mon, 7 Oct 2002 13:03:18 -0400 (EDT) From: "Robert E. Gruber" To: "Janet Tvedt" , Cc: "Robert E. Gruber" Subject: RE: [omniNotify] org.omg.CosNotifyComm.InvalidEventType Message-ID: <000801c26e23$25281610$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <200210050036.RAA12117@pertelote.tuc.noao.edu> Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Oct 7 18:04:00 2002 X-Original-Date: Mon, 7 Oct 2002 13:01:14 -0400 Janet, thanks for pointing this out, I think you found something that is not implemented correctly. offer_change/subscription_change both check that the lists of added/deleted event types are 'valid'. Currently this check is probably too restrictive: other than special forms (such as '*', '%ALL', '%TYPED') only names that consist of alphanumerics and underscore are accepted. I believe the main issue is that wildcards together with other chars (such as "foo*" or "*foo" or "foo*bar") should be rejected because the only wildcard support at the moment is when just '*' by itself is used. I think dot notation *should* be allowed, and probably any string that does not include a wildcard (plus other chars) should be allowed. (I could not find any restrictions on the strings used as domain/type name in the spec, but I only scanned it for about 10 minutes before giving up. If someone knows of any restrictions, please let me know.) So, I will make an update and post something when it is available. -- Bob P.S. Not tested yet, but I am 99% sure the fix is to remove these 30 lines from RDIEvent.h: if ( RDI_STR_NEQ(tseq[ix].type_name, "*") && RDI_STR_NEQ(tseq[ix].type_name, "%ANY") && RDI_STR_NEQ(tseq[ix].type_name, "%TYPED") ) { // first char must be alpha or underscore if (!RDI_IS_ALPHA_OR_UNDERSCORE(tseq[ix].type_name[(CORBA::ULong)0])) { invalid_index = ix; return 0; } // remaining chars must be alphanum or underscore for (i = 1; i < RDI_STRLEN(tseq[ix].type_name); i++) { if ( !RDI_IS_ALPHANUM_OR_UNDERSCORE(tseq[ix].type_name[i]) ) { invalid_index = ix; return 0; } } } if ( RDI_STR_NEQ(tseq[ix].domain_name, "*") ) { // first char must be alpha or underscore if (!RDI_IS_ALPHA_OR_UNDERSCORE(tseq[ix].domain_name[(CORBA::ULong)0])) { invalid_index = ix; return 0; } // remaining chars must be alphanum or underscore for (i = 1; i < RDI_STRLEN(tseq[ix].domain_name); i++) { if ( !RDI_IS_ALPHANUM_OR_UNDERSCORE(tseq[ix].domain_name[i]) ) { invalid_index = ix; return 0; } } } -----Original Message----- From: omninotify-list-admin@omniorb-support.com [mailto:omninotify-list-admin@omniorb-support.com]On Behalf Of Janet Tvedt Sent: Friday, October 04, 2002 8:36 PM To: omninotify-list@realvnc.com Subject: [omniNotify] org.omg.CosNotifyComm.InvalidEventType I am getting an org.omg.CosNotifyComm.InvalidEventType exception when a StructuredPushSupplier calls offer_change with an EventType("foo.bar", "baz"). However, EventType("foo", "baz") works fine. This dotted naming scheme is working fine for sending/receiving structured events, even with filters. So I am puzzled as to why it doesn't work in this context. Any ideas? -------------------------------------------------------------------------- Janet Tvedt, National Solar Observatory/SOLIS Email: tvedt@noao.edu P.O. Box 26732, Tucson, AZ 85732-6732 Phone: (520) 318-8388 950 N. Cherry Ave., Tucson, AZ 85719 FAX: (520) 318-8278 _______________________________________________ omninotify-list mailing list omninotify-list@omniorb-support.com http://www.omniorb-support.com/mailman/listinfo/omninotify-list From Matthew.Berry@aspentech.com Tue Oct 8 15:23:17 2002 Received: from ukcmailgwi1.atuk.aspentech.com (nat20895-108.aspentech.com [208.201.95.108]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g98ENH829734 for ; Tue, 8 Oct 2002 15:23:17 +0100 Received: by UKCMAILGWI1 with Internet Mail Service (5.5.2653.19) id ; Tue, 8 Oct 2002 15:23:16 +0100 Message-ID: <4E6024B5C5C7D51185650002B330B4B85AF67D@londonmail.lon.aspentech.com> From: Matthew Berry To: omninotify-list@omniorb-support.com MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [omniNotify] Development Status Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Tue Oct 8 15:24:00 2002 X-Original-Date: Tue, 8 Oct 2002 15:23:14 +0100 Bob, Can you please give us an update on the development currently underway for omniNotify. When is the next release and what is it likely to contain? Thanks Matthew From gruber@research.att.com Thu Oct 10 15:19:40 2002 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g9AEJd821396 for ; Thu, 10 Oct 2002 15:19:40 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id C94554CE29; Thu, 10 Oct 2002 10:19:36 -0400 (EDT) Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.8.8/8.8.8) with SMTP id KAA24609; Thu, 10 Oct 2002 10:19:36 -0400 (EDT) From: "Robert E. Gruber" To: "Matthew Berry" , Cc: "Robert E. Gruber" Subject: RE: [omniNotify] Development Status Message-ID: <000d01c27067$c4551d50$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <4E6024B5C5C7D51185650002B330B4B85AF67D@londonmail.lon.aspentech.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Oct 10 15:20:00 2002 X-Original-Date: Thu, 10 Oct 2002 10:17:29 -0400 Unfortunately, I have a lot less time for omniNotify development than I used to. Perhaps I've been somewhat in denial about this which is why I haven't mentioned it earlier. This means any major new features will not happen without outside help. Below are the things I still plan to do this year myself (although I do ask for autoconf help :->)... The official omniNotify 2.0 release will be just like the current 2.0.ALPHA release (plus the small fix recently requested by Janet), except I think it would be good to get autoconf support working. Right now you need to use the older omniORB build scheme. Is there anyone out there with autoconf expertise willing to do this part of the project for me? I am really pressed for time at the moment. The next step, for omniNotify 2.1, is to do a Windows NT/2000 port. As others have pointed out recently, you can run the notification daemon, notifd, on a linux/other box and run all of the suppliers and consumers that you like on Windows boxen, so it is not a total loss for Windows folks that there is no Windows port yet for the notification daemon. Of course some people want to run everything on one machine, so a port would be nice. I cannot give a time frame for this port as my other work keeps piling up, and I have to take care of that first. It looks like I will have time to work on this in December. If I start working on it sooner than that I will send out another note indicating when I expect to get something out. -- Bob -----Original Message----- From: omninotify-list-admin@omniorb-support.com [mailto:omninotify-list-admin@omniorb-support.com]On Behalf Of Matthew Berry Sent: Tuesday, October 08, 2002 10:23 AM To: omninotify-list@omniorb-support.com Subject: [omniNotify] Development Status Bob, Can you please give us an update on the development currently underway for omniNotify. When is the next release and what is it likely to contain? Thanks Matthew _______________________________________________ omninotify-list mailing list omninotify-list@omniorb-support.com http://www.omniorb-support.com/mailman/listinfo/omninotify-list From Matthew.Berry@aspentech.com Thu Oct 10 15:27:58 2002 Received: from ukcmailgwi1.atuk.aspentech.com (nat20895-219.aspentech.com [208.201.95.219]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g9AERw821782 for ; Thu, 10 Oct 2002 15:27:58 +0100 Received: by ukcmailgwi1.atuk.aspentec.com with Internet Mail Service (5.5.2653.19) id <4S3AJH1X>; Thu, 10 Oct 2002 15:27:45 +0100 Message-ID: <4E6024B5C5C7D51185650002B330B4B85AF787@londonmail.lon.aspentech.com> From: Matthew Berry To: "Robert E. Gruber" , omninotify-list@omniorb-support.com Subject: RE: [omniNotify] Development Status MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Oct 10 15:28:00 2002 X-Original-Date: Thu, 10 Oct 2002 15:27:43 +0100 Bob, Thanks for your reply - glad to hear omniNotify is still being worked on, albeit slowly. Correct me if I am wrong, by I don't think omniNotify supports persistent events at the moment. Have you considered this for future development? Thanks again Matthew > -----Original Message----- > From: Robert E. Gruber [mailto:gruber@research.att.com] > Sent: 10 October 2002 15:17 > To: Matthew Berry; omninotify-list@omniorb-support.com > Cc: Robert E. Gruber > Subject: RE: [omniNotify] Development Status > > > Unfortunately, I have a lot less time for omniNotify development > than I used to. Perhaps I've been somewhat in denial about this > which is why I haven't mentioned it earlier. > > This means any major new features will not > happen without outside help. Below are the things I still plan > to do this year myself (although I do ask for autoconf help :->)... > > The official omniNotify 2.0 release will be just like the > current 2.0.ALPHA release (plus the small > fix recently requested by Janet), except I think it would be > good to get autoconf support working. Right now you need > to use the older omniORB build scheme. > > Is there anyone out there with autoconf expertise willing > to do this part of the project for me? I am really pressed > for time at the moment. > > The next step, for omniNotify 2.1, is to do a > Windows NT/2000 port. > > As others have pointed out recently, > you can run the notification daemon, notifd, > on a linux/other box and run all of the suppliers > and consumers that you like on Windows boxen, so it is > not a total loss for Windows folks that there is no Windows > port yet for the notification daemon. Of course > some people want to run everything on one machine, so > a port would be nice. > > I cannot give a time frame for this port > as my other work keeps piling up, > and I have to take care of that first. > It looks like I will have time to work > on this in December. If I start working on it sooner > than that I will send out another > note indicating when I expect to get something out. > > -- Bob > > -----Original Message----- > From: omninotify-list-admin@omniorb-support.com > [mailto:omninotify-list-admin@omniorb-support.com]On Behalf Of Matthew > Berry > Sent: Tuesday, October 08, 2002 10:23 AM > To: omninotify-list@omniorb-support.com > Subject: [omniNotify] Development Status > > Bob, > > Can you please give us an update on the development currently > underway for > omniNotify. When is the next release and what is it likely to contain? > > Thanks > Matthew > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > From gruber@research.att.com Thu Oct 10 15:48:44 2002 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id g9AEmh822701 for ; Thu, 10 Oct 2002 15:48:43 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id EA44D4CE5D; Thu, 10 Oct 2002 10:48:40 -0400 (EDT) Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.8.8/8.8.8) with SMTP id KAA28895; Thu, 10 Oct 2002 10:48:40 -0400 (EDT) From: "Robert E. Gruber" To: "Matthew Berry" Cc: "Robert E. Gruber" , Subject: RE: [omniNotify] Development Status Message-ID: <000e01c2706b$d3e00240$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <4E6024B5C5C7D51185650002B330B4B85AF787@londonmail.lon.aspentech.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Oct 10 15:49:00 2002 X-Original-Date: Thu, 10 Oct 2002 10:46:33 -0400 Yes, reliability and persistence are two things that I would love to work on. I almost put them down except I wanted to stick to things I know I can get done in 2002. The other thing I did not put down is performance improvements. With omniORB4 there are some very interesting things one could do. (I think omniNotify is already fast compared to some other notification services, but making it even faster would be fun.) Some obvious approaches to event persistence are: 1. use the file system 2. use an open source DB directly 3. drive any DB using an open source ODBC driver I suspect these options are ordered from fastest to slowest (but least to most flexible), but I would have to do experiments to find out. Work on this is not happening soon, I'm afraid, unless someone else does it. -- Bob -----Original Message----- From: Matthew Berry [mailto:Matthew.Berry@aspentech.com] Sent: Thursday, October 10, 2002 10:28 AM To: Robert E. Gruber; omninotify-list@omniorb-support.com Subject: RE: [omniNotify] Development Status Bob, Thanks for your reply - glad to hear omniNotify is still being worked on, albeit slowly. Correct me if I am wrong, by I don't think omniNotify supports persistent events at the moment. Have you considered this for future development? Thanks again Matthew From goetz@esrf.fr Thu Jan 30 08:48:47 2003 Received: from out.esrf.fr (firewall.esrf.fr [193.49.43.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with SMTP id h0U8ml831380 for ; Thu, 30 Jan 2003 08:48:47 GMT Received: (from uucp@localhost) by out.esrf.fr (8.6.10/8.6.10) id JAA23429 for ; Thu, 30 Jan 2003 09:46:03 +0100 Received: from esrf.esrf.fr(160.103.2.9) by firewall via smap (V1.3) id tmp023341; Thu Jan 30 09:45:36 2003 Received: from maya.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id JAA24808 for ; Thu, 30 Jan 2003 09:48:12 +0100 (MET) Received: from localhost (goetz@localhost) by maya.esrf.fr (8.9.3+Sun/8.9.1) with ESMTP id JAA10686 for ; Thu, 30 Jan 2003 09:48:11 +0100 (MET) X-Authentication-Warning: maya.esrf.fr: goetz owned process doing -bs From: Andy Goetz X-Sender: goetz@maya To: omninotify-list@omniorb-support.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [omniNotify] resolving Notification Service Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Jan 30 08:49:02 2003 X-Original-Date: Thu, 30 Jan 2003 09:48:11 +0100 (MET) Hi, I am new to omniNotify so please be patient if my question has an obvious answer. I am trying to get a VERY simple example working with a server and client for omniNotify building them from scratch. I have hacked the examples code to send my own events but I do not find it very clear. I would like to write a server and client from scratch using the COS Notification API directly. My first example fails just trying to get the EventChannelFactory. My code to get a handle on the EventChannelFactory looks like this : CosNotifyChannelAdmin::EventChannel_var eventChannelFactory; try { CORBA::Object_var obj = orb -> resolve_initial_references("NotificationService"); // // Narrow the CORBA_Object reference to an EventChannelFactory // reference so we can invoke its methods // eventChannelFactory = CosNotifyChannelAdmin::EventChannelFactory::_narrow(obj); } catch(...) { cerr << "Cannot resolve `NotificationService'" << endl; exit(1); } // // Make sure the CORBA object was really an EventChannelFactory // if(CORBA::is_nil(eventChannelFactory)) { cerr << "`NotificationService' initial reference is not " << "a CosNotifyChannelAdmin::EventChannelFactory" << endl; exit(1); } But it never resolves the EventChannelFactory. I have tried resolving the IOR in the /tmp/rdifact.ior file as well but when I do the narrow it says this is not an EventChannelFactory. My questions are : (1) is the bootstrap method via "NotificationService" supported ? (2) why can I not narrow /tmp/rdifact.ior to CosNotifyChannelAdmin::EventChannelFactory ? Thanks for any help you can give on this. Andy Gotz -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From goetz@esrf.fr Thu Jan 30 10:26:30 2003 Received: from out.esrf.fr (firewall.sfn.asso.fr [193.49.43.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with SMTP id h0UAQU803654 for ; Thu, 30 Jan 2003 10:26:30 GMT Received: (from uucp@localhost) by out.esrf.fr (8.6.10/8.6.10) id LAA22897 for ; Thu, 30 Jan 2003 11:23:48 +0100 Received: from esrf.esrf.fr(160.103.2.9) by firewall via smap (V1.3) id tmp022798; Thu Jan 30 11:23:29 2003 Subject: Re: [omniNotify] resolving Notification Service Received: from maya.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id LAA26659 for ; Thu, 30 Jan 2003 11:26:06 +0100 (MET) Received: from localhost (goetz@localhost) by maya.esrf.fr (8.9.3+Sun/8.9.1) with ESMTP id LAA11549 for ; Thu, 30 Jan 2003 11:26:06 +0100 (MET) X-Authentication-Warning: maya.esrf.fr: goetz owned process doing -bs From: Andy Goetz X-Sender: goetz@maya To: omninotify-list@omniorb-support.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Jan 30 10:27:01 2003 X-Original-Date: Thu, 30 Jan 2003 11:26:05 +0100 (MET) Hi, I have partly resolved my problem of bootstrapping. In my program which was converting the ior to an EventChannel I had mistyped /tmp/rdfact.ior and /tmp/rdchan.ior ! Once I had corrected this stupid mistake I could correctly resolve these two references to their correct types. I still cannot get the resolve_initial_references on "NotificationService" to work however. Is this supposed to work ? I do not see it being used in any of the examples. Now I get a CORBA::SystemException when I try to : structuredProxyPushConsumer -> connect_structured_push_supplier( CosNotifyComm::StructuredPushSupplier::_nil()); Up to then everything seems to work fine. Any ideas about what the beginner is doing wrong again ? Thanks Andy On Thu, 30 Jan 2003, Andy Goetz wrote: > Hi, > > I am new to omniNotify so please be patient if my question has an obvious > answer. > > I am trying to get a VERY simple example working with a server and client > for omniNotify building them from scratch. I have hacked the examples code > to send my own events but I do not find it very clear. I would like to > write a server and client from scratch using the COS Notification API > directly. My first example fails just trying to get the > EventChannelFactory. > > My code to get a handle on the EventChannelFactory looks like this : > > CosNotifyChannelAdmin::EventChannel_var eventChannelFactory; > try > { > CORBA::Object_var obj = > orb -> resolve_initial_references("NotificationService"); > > // > // Narrow the CORBA_Object reference to an EventChannelFactory > // reference so we can invoke its methods > // > eventChannelFactory = > CosNotifyChannelAdmin::EventChannelFactory::_narrow(obj); > > } > catch(...) > { > cerr << "Cannot resolve `NotificationService'" << endl; > exit(1); > } > > // > // Make sure the CORBA object was really an EventChannelFactory > // > if(CORBA::is_nil(eventChannelFactory)) > { > cerr << "`NotificationService' initial reference is not " > << "a CosNotifyChannelAdmin::EventChannelFactory" > << endl; > exit(1); > } > > But it never resolves the EventChannelFactory. I have tried resolving the > IOR in the /tmp/rdifact.ior file as well but when I do the narrow it says > this is not an EventChannelFactory. > > My questions are : > > (1) is the bootstrap method via "NotificationService" supported ? > > (2) why can I not narrow /tmp/rdifact.ior to > > CosNotifyChannelAdmin::EventChannelFactory ? > > Thanks for any help you can give on this. > > Andy Gotz > > -- > European Synchrotron Radiation Facility > 6, rue Jules Horowitz, > Grenoble, 38043 > FRANCE > > tel: (+33)-476882646 > > email: goetz@esrf.fr > andy_gotz@yahoo.fr > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From tvedt@noao.edu Thu Jan 30 16:23:49 2003 Received: from noao.edu (email.noao.edu [140.252.1.54]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h0UGNm821167 for ; Thu, 30 Jan 2003 16:23:49 GMT Received: from dorado.tuc.noao.edu ([140.252.38.7] verified) by noao.edu (CommuniGate Pro SMTP 4.0.3) with ESMTP-TLS id 6381865; Thu, 30 Jan 2003 09:23:50 -0700 Received: from dorado.tuc.noao.edu (localhost [127.0.0.1]) by dorado.tuc.noao.edu (8.12.5/8.12.5) with ESMTP id h0UGL4Ob003372; Thu, 30 Jan 2003 09:21:04 -0700 Received: (from tvedt@localhost) by dorado.tuc.noao.edu (8.12.5/8.12.5/Submit) id h0UGL4uY003370; Thu, 30 Jan 2003 09:21:04 -0700 X-Authentication-Warning: dorado.tuc.noao.edu: tvedt set sender to tvedt@noao.edu using -f Subject: Re: [omniNotify] resolving Notification Service From: Janet Tvedt To: Andy Goetz Cc: omninotify-list@omniorb-support.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Message-Id: <1043943664.2801.1187.camel@dorado.tuc.noao.edu> Mime-Version: 1.0 Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Jan 30 16:24:02 2003 X-Original-Date: 30 Jan 2003 09:21:04 -0700 Andy, I don't know the answer to your question about whether or not you should/can use resolve_initial_references to find the notification service. However, you can use this call to find the naming service: CORBA::Object_var name_service; CosNaming::NamingContext_var name_context; name_service = orb->resolve_initial_references("NameService"); name_context = CosNaming::NamingContext::_narrow(name_service); Then use the name service to locate the channel factory and/or default event channel: CosNaming::Name name; name.length(1); name[0].id = CORBA::string_dup((const char*)"EventChannel"); name[0].kind = CORBA::string_dup((const char*)"EventChannel"); CORBA::Object_var channel_ref = name_context->resolve(name); Have a look at at omniNotify/examples/get_channel.h for details. Janet Tvedt On Thu, 2003-01-30 at 03:26, Andy Goetz wrote: > Hi, > > I have partly resolved my problem of bootstrapping. In my program which > was converting the ior to an EventChannel I had mistyped /tmp/rdfact.ior > and /tmp/rdchan.ior ! Once I had corrected this stupid mistake I could > correctly resolve these two references to their correct types. I still > cannot get the resolve_initial_references on "NotificationService" to > work however. Is this supposed to work ? I do not see it being used in > any of the examples. > > Now I get a CORBA::SystemException when I try to : > > structuredProxyPushConsumer -> connect_structured_push_supplier( > CosNotifyComm::StructuredPushSupplier::_nil()); > > Up to then everything seems to work fine. Any ideas about what the > beginner is doing wrong again ? > > Thanks > > Andy > > On Thu, 30 Jan 2003, Andy Goetz wrote: > > > Hi, > > > > I am new to omniNotify so please be patient if my question has an obvious > > answer. > > > > I am trying to get a VERY simple example working with a server and client > > for omniNotify building them from scratch. I have hacked the examples code > > to send my own events but I do not find it very clear. I would like to > > write a server and client from scratch using the COS Notification API > > directly. My first example fails just trying to get the > > EventChannelFactory. > > > > My code to get a handle on the EventChannelFactory looks like this : > > > > CosNotifyChannelAdmin::EventChannel_var eventChannelFactory; > > try > > { > > CORBA::Object_var obj = > > orb -> resolve_initial_references("NotificationService"); > > > > // > > // Narrow the CORBA_Object reference to an EventChannelFactory > > // reference so we can invoke its methods > > // > > eventChannelFactory = > > CosNotifyChannelAdmin::EventChannelFactory::_narrow(obj); > > > > } > > catch(...) > > { > > cerr << "Cannot resolve `NotificationService'" << endl; > > exit(1); > > } > > > > // > > // Make sure the CORBA object was really an EventChannelFactory > > // > > if(CORBA::is_nil(eventChannelFactory)) > > { > > cerr << "`NotificationService' initial reference is not " > > << "a CosNotifyChannelAdmin::EventChannelFactory" > > << endl; > > exit(1); > > } > > > > But it never resolves the EventChannelFactory. I have tried resolving the > > IOR in the /tmp/rdifact.ior file as well but when I do the narrow it says > > this is not an EventChannelFactory. > > > > My questions are : > > > > (1) is the bootstrap method via "NotificationService" supported ? > > > > (2) why can I not narrow /tmp/rdifact.ior to > > > > CosNotifyChannelAdmin::EventChannelFactory ? > > > > Thanks for any help you can give on this. > > > > Andy Gotz > > > > -- > > European Synchrotron Radiation Facility > > 6, rue Jules Horowitz, > > Grenoble, 38043 > > FRANCE > > > > tel: (+33)-476882646 > > > > email: goetz@esrf.fr > > andy_gotz@yahoo.fr > > > > _______________________________________________ > > omninotify-list mailing list > > omninotify-list@omniorb-support.com > > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > > > > -- > European Synchrotron Radiation Facility > 6, rue Jules Horowitz, > Grenoble, 38043 > FRANCE > > tel: (+33)-476882646 > > email: goetz@esrf.fr > andy_gotz@yahoo.fr > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list From goetz@esrf.fr Thu Jan 30 21:53:03 2003 Received: from out.esrf.fr (firewall.ill.fr [193.49.43.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with SMTP id h0ULr3804560 for ; Thu, 30 Jan 2003 21:53:03 GMT Received: (from uucp@localhost) by out.esrf.fr (8.6.10/8.6.10) id WAA27820; Thu, 30 Jan 2003 22:50:20 +0100 Received: from esrf.esrf.fr(160.103.2.9) by firewall via smap (V1.3) id tmp027620; Thu Jan 30 22:50:06 2003 Subject: Re: [omniNotify] resolving Notification Service Received: from maya.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id WAA29598; Thu, 30 Jan 2003 22:52:44 +0100 (MET) Received: from localhost (goetz@localhost) by maya.esrf.fr (8.9.3+Sun/8.9.1) with ESMTP id WAA15753; Thu, 30 Jan 2003 22:52:43 +0100 (MET) X-Authentication-Warning: maya.esrf.fr: goetz owned process doing -bs From: Andy Goetz X-Sender: goetz@maya To: Janet Tvedt cc: omninotify-list@omniorb-support.com In-Reply-To: <1043943664.2801.1187.camel@dorado.tuc.noao.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Jan 30 21:54:01 2003 X-Original-Date: Thu, 30 Jan 2003 22:52:43 +0100 (MET) Hi, thanks a lot for the answer. I think my problem now is with the connect_structured_push_supplier(). All examples I have seen show you can use CosNotifyComm::StructuredSupplier::_nil() as argument but it fails with a CORBA:SystemException under omniNotify 1.2. I do not fully understand the example which is delivered with omniNotify. Things like _this() are a mystery to me. That is why I tried to write a simple example from scratch. I guess I will have to hack the omniNotify example to get something working even if I don't understand all the code. Andy On 30 Jan 2003, Janet Tvedt wrote: > Andy, > > I don't know the answer to your question about whether or not you > should/can use resolve_initial_references to find the notification > service. However, you can use this call to find the naming service: > > CORBA::Object_var name_service; > CosNaming::NamingContext_var name_context; > name_service = orb->resolve_initial_references("NameService"); > name_context = CosNaming::NamingContext::_narrow(name_service); > > Then use the name service to locate the channel factory and/or default > event channel: > > CosNaming::Name name; > name.length(1); > name[0].id = CORBA::string_dup((const char*)"EventChannel"); > name[0].kind = CORBA::string_dup((const char*)"EventChannel"); > CORBA::Object_var channel_ref = name_context->resolve(name); > > Have a look at at omniNotify/examples/get_channel.h for details. > > Janet Tvedt > -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From Cameron.Rochester@Ripple-Systems.com Thu Feb 13 03:05:52 2003 Received: from webmailme.motherwell.com.au ([203.17.161.11]) by raq2100.uk2net.com (8.10.2/8.10.2) with SMTP id h1D35o821400 for ; Thu, 13 Feb 2003 03:05:50 GMT Received: (qmail 12144 invoked by uid 1007); 13 Feb 2003 03:05:08 -0000 Received: from Cameron.Rochester@Ripple-Systems.com by webmailme by uid 1004 with qmail-scanner-1.15 (uvscan: v4.1.60/v4247. Clear:. Processed in 2.324492 secs); 13 Feb 2003 03:05:08 -0000 Received: from unknown (HELO envelope.pth.motherwell.com.au) (192.168.70.14) by webmailme.motherwell.com.au with SMTP; 13 Feb 2003 03:05:04 -0000 Received: by envelope.pth.motherwell.com.au with Internet Mail Service (5.5.2653.19) id <1DXZX51B>; Thu, 13 Feb 2003 11:05:04 +0800 Message-ID: From: Cameron Rochester To: "'omninotify-list@omniorb-support.com'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [omniNotify] Mapping Filters and Persistence Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Feb 13 03:06:01 2003 X-Original-Date: Thu, 13 Feb 2003 11:04:55 +0800 Hi, I am currently investigating Notification Services and have a few questions about omniNotify. 1) I realise that persistence (EventReliability or ConnectionReliability) is not supported currently. Is there any work being done in this area at the moment? Do you have any idea how much effort would be involved in implementing this? 2) Are mapping filters supported? My question about mapping filters arises from our need to federate Notificatio Services. The main problem we foresee is Event 'feedback' where you have a Notification Service both supplying and consuming events from another Nofitication service. One option would be to use a 'hop count', or 'supplied from' field in the filterable data that can be used to prevent 'feedback'. I think this may be achievable using mapping filters but I am not entirely sure. Does anyone have any suggested solutions to the problem - or point me in the direction of some info that could help. Regards Cameron Rochester Software Engineer Ripple Systems Pty Ltd Ph: +61 893688616 Fax: +61 893688699 From gruber@research.att.com Thu Feb 13 14:15:18 2003 Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h1DEFI821539 for ; Thu, 13 Feb 2003 14:15:18 GMT Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-green.research.att.com (Postfix) with ESMTP id 6FD981E00A; Thu, 13 Feb 2003 09:15:14 -0500 (EST) Received: from raptor.research.att.com (raptor.research.att.com [135.207.23.32]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h1DEFEO03864; Thu, 13 Feb 2003 09:15:14 -0500 (EST) From: "Robert E. Gruber" To: Cameron Rochester Cc: Subject: Re: [omniNotify] Mapping Filters and Persistence In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Feb 13 14:16:01 2003 X-Original-Date: Thu, 13 Feb 2003 09:15:13 -0500 I do not plan to implement persistence any time soon, but perhaps someone else might be interested. This would not be a trivial project. If someone wanted to work on it, I would be willing to support that effort by answering questions and helping to resolve issues as they come up. Mapping filters: I believe they only map certain values, timeout and priority, neither of which would work as a 'supplied from' field. I think there is an OMG spec on managing networks of event channels. omniNotify does not support it, but you might at least look at it and check which notification services do support it. -- Bob On Thu, 13 Feb 2003, Cameron Rochester wrote: > Hi, > > I am currently investigating Notification Services and have a few questions > about omniNotify. > > 1) I realise that persistence (EventReliability or ConnectionReliability) is > not supported currently. Is there any work being done in this area at the > moment? Do you have any idea how much effort would be involved in > implementing this? > > 2) Are mapping filters supported? > > My question about mapping filters arises from our need to federate > Notificatio Services. The main problem we foresee is Event 'feedback' where > you have a Notification Service both supplying and consuming events from > another Nofitication service. One option would be to use a 'hop count', or > 'supplied from' field in the filterable data that can be used to prevent > 'feedback'. I think this may be achievable using mapping filters but I am > not entirely sure. Does anyone have any suggested solutions to the problem - > or point me in the direction of some info that could help. > > Regards > Cameron Rochester > > Software Engineer > Ripple Systems Pty Ltd > Ph: +61 893688616 > Fax: +61 893688699 > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > From goetz@esrf.fr Mon Feb 24 09:24:39 2003 Received: from out.esrf.fr (firewall.ill.fr [193.49.43.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with SMTP id h1O9Od829045 for ; Mon, 24 Feb 2003 09:24:39 GMT Received: (from uucp@localhost) by out.esrf.fr (8.6.10/8.6.10) id KAA10275 for ; Mon, 24 Feb 2003 10:21:26 +0100 Received: from esrf.esrf.fr(160.103.2.9) by firewall via smap (V1.3) id tmp010171; Mon Feb 24 10:21:11 2003 Received: from maya.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id KAA18095 for ; Mon, 24 Feb 2003 10:24:11 +0100 (MET) Received: from localhost (goetz@localhost) by maya.esrf.fr (8.9.3+Sun/8.9.1) with ESMTP id KAA05382 for ; Mon, 24 Feb 2003 10:24:10 +0100 (MET) X-Authentication-Warning: maya.esrf.fr: goetz owned process doing -bs From: Andy Goetz X-Sender: goetz@maya cc: omninotify-list@omniorb-support.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [omniNotify] omniNotify for Windows platforms Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Feb 24 09:25:03 2003 X-Original-Date: Mon, 24 Feb 2003 10:24:10 +0100 (MET) Hi, I would like to use omniNotify (as client and notify daemon) on Windows. Has anyone tried this ? What would it entail to port omniNotify to Windows if it hasn't been done so already ? Thanks, Andy -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From gruber@research.att.com Mon Feb 24 18:54:24 2003 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h1OIsO824374 for ; Mon, 24 Feb 2003 18:54:24 GMT Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id 9B8D64CF9A; Mon, 24 Feb 2003 13:54:21 -0500 (EST) Received: from raptor.research.att.com (raptor.research.att.com [135.207.23.32]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h1OIsJB00171; Mon, 24 Feb 2003 13:54:19 -0500 (EST) From: "Robert E. Gruber" To: Andy Goetz Cc: Subject: Re: [omniNotify] omniNotify for Windows platforms In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Feb 24 18:55:02 2003 X-Original-Date: Mon, 24 Feb 2003 13:54:19 -0500 You can of course write clients that run on Windows, it is only the daemon (notifd) that requires some porting effort. I would love to do the port but I do not have time. My standard suggestion is to run notifd on a linux box and your clients on Windows. I suspect the hard part about porting would be changing the make files to get all the debug/nondebug DLL stuff working correctly. (I have not had time to convert omniNotify to use the newer autoconf approach introduced for omniORB 4, and really it makes the most sense to do a Windows port after doing that conversion, to take advantage of what autoconf gives you.) In terms of actual code changes, I doubt there would be too many. There would some include fixes, and maybe a couple cases where a unix-only system call is used. -- Bob On Mon, 24 Feb 2003, Andy Goetz wrote: > Hi, > > I would like to use omniNotify (as client and notify daemon) on Windows. > Has anyone tried this ? What would it entail to port omniNotify to Windows > if it hasn't been done so already ? > > Thanks, > > Andy > > -- > European Synchrotron Radiation Facility > 6, rue Jules Horowitz, > Grenoble, 38043 > FRANCE > > tel: (+33)-476882646 > > email: goetz@esrf.fr > andy_gotz@yahoo.fr > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > From duncan@grisby.org Tue Feb 25 12:39:12 2003 Received: from grisby.dyndns.org (pc2-cmbg4-5-cust210.cmbg.cable.ntl.com [81.96.73.210]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h1PCdB811461 for ; Tue, 25 Feb 2003 12:39:11 GMT Received: from grisby.org (dpg1@localhost) by grisby.dyndns.org (8.11.6/8.11.6) with ESMTP id h1PCcYD13240 for ; Tue, 25 Feb 2003 12:38:34 GMT Message-Id: <200302251238.h1PCcYD13240@grisby.dyndns.org> X-Authentication-Warning: pc2-cmbg4-5-cust210.cmbg.cable.ntl.com: dpg1 owned process doing -bs To: omninotify-list@omniorb-support.com Subject: Re: [omniNotify] omniNotify for Windows platforms In-Reply-To: Message from "Robert E. Gruber" of "Mon, 24 Feb 2003 13:54:19 EST." From: Duncan Grisby Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Tue Feb 25 12:40:02 2003 X-Original-Date: Tue, 25 Feb 2003 12:38:34 +0000 On Monday 24 February, "Robert E. Gruber" wrote: > I suspect the hard part about porting would be changing the > make files to get all the debug/nondebug DLL stuff working > correctly. (I have not had time to convert omniNotify > to use the newer autoconf approach introduced for omniORB 4, > and really it makes the most sense to do a Windows port > after doing that conversion, to take advantage of what > autoconf gives you.) Autoconf isn't used on Windows. The Windows build still uses the old scheme with platform makefiles. Cheers, Duncan. -- -- Duncan Grisby -- -- duncan@grisby.org -- -- http://www.grisby.org -- From goetz@esrf.fr Mon Mar 3 21:35:38 2003 Received: from out.esrf.fr (firewall.sfn.asso.fr [193.49.43.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h23LZc806061 for ; Mon, 3 Mar 2003 21:35:38 GMT Received: (from uucp@localhost) by out.esrf.fr (1.0.0) id h23LZZ217582; Mon, 3 Mar 2003 22:35:35 +0100 (MET) Received: from esrf.esrf.fr(160.103.2.9) by out.esrf.fr via smap (V1.3) id tmp017500; Mon Mar 3 22:35:11 2003 Subject: Re: [omniNotify] omniNotify for Windows platforms Received: from maya.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id WAA08749; Mon, 3 Mar 2003 22:35:09 +0100 (MET) Received: from localhost (goetz@localhost) by maya.esrf.fr (8.9.3+Sun/8.9.1) with ESMTP id WAA08926; Mon, 3 Mar 2003 22:35:08 +0100 (MET) X-Authentication-Warning: maya.esrf.fr: goetz owned process doing -bs From: Andy Goetz X-Sender: goetz@maya To: "Robert E. Gruber" cc: omninotify-list@omniorb-support.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Mon Mar 3 21:36:00 2003 X-Original-Date: Mon, 3 Mar 2003 22:35:08 +0100 (MET) Hi, when you say clients can run on Windows I presume you mean that clients only need the idl interface compiled for Windows. Is this true ? If so which files are these. I can only find AttNotification.idl. Is this all Notification clients need ? Does the same hold true for java clients ? What do java clients need to link with in order to use the Notification service as clients ? Thanks for your help, Andy Gotz (ESRF) On Mon, 24 Feb 2003, Robert E. Gruber wrote: > > You can of course write clients that run on Windows, it is > only the daemon (notifd) that requires some porting effort. > I would love to do the port but I do not have time. > My standard suggestion is to run notifd on a linux box > and your clients on Windows. > > I suspect the hard part about porting would be changing the > make files to get all the debug/nondebug DLL stuff working > correctly. (I have not had time to convert omniNotify > to use the newer autoconf approach introduced for omniORB 4, > and really it makes the most sense to do a Windows port > after doing that conversion, to take advantage of what > autoconf gives you.) > > In terms of actual code changes, I doubt there > would be too many. There would some include > fixes, and maybe a couple cases where a unix-only > system call is used. > > -- Bob > > On Mon, 24 Feb 2003, Andy Goetz wrote: > > > Hi, > > > > I would like to use omniNotify (as client and notify daemon) on Windows. > > Has anyone tried this ? What would it entail to port omniNotify to Windows > > if it hasn't been done so already ? > > > > Thanks, > > > > Andy > > > > -- > > European Synchrotron Radiation Facility > > 6, rue Jules Horowitz, > > Grenoble, 38043 > > FRANCE > > > > tel: (+33)-476882646 > > > > email: goetz@esrf.fr > > andy_gotz@yahoo.fr > > > > _______________________________________________ > > omninotify-list mailing list > > omninotify-list@omniorb-support.com > > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > > > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From markzimm@io.frii.com Thu Mar 13 21:15:51 2003 Received: from io.frii.com (io.frii.com [216.17.222.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h2DLFoV22240 for ; Thu, 13 Mar 2003 21:15:50 GMT Received: from io.frii.com (localhost.frii.com [127.0.0.1]) by io.frii.com (8.12.8/8.12.8) with ESMTP id h2DLFo6f065573 for ; Thu, 13 Mar 2003 14:15:50 -0700 (MST) Received: (from markzimm@localhost) by io.frii.com (8.12.8/8.12.8/Submit) id h2DLForv065572 for omninotify-list@omniorb-support.com; Thu, 13 Mar 2003 14:15:50 -0700 (MST) From: Mark Zimmerman To: omninotify-list@omniorb-support.com Message-ID: <20030313211550.GB63162@io.frii.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: [omniNotify] omniORB 4.0.1, omniNotify 2.0 alpha, and AIX Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Mar 13 21:16:01 2003 X-Original-Date: Thu, 13 Mar 2003 14:15:50 -0700 Greetings: I am trying to compile omniNotify 2.0 alpha with omniORB 4.0.1 on an AIX machine. There are some problems with library dependencies that the attached patch seems to work around. I am sure that this is not the correct answer to the problem but it may be of informational value. The problems occur when linking libAttNotificationDynamic4.a.0 and libCOSDynamic4.a.0. Both have a multitude of unresolved externals that are resolved by adding a library to the link. This is not necessary under Solaris or Linux. Also, in both cases the following linker warnings are reported: ld: 0711-415 WARNING: Symbol __cdtors is already exported. ld: 0711-415 WARNING: Symbol __priority0x80000028 is already exported. -- Mark From markzimm@io.frii.com Thu Mar 13 21:31:11 2003 Received: from io.frii.com (io.frii.com [216.17.222.1]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h2DLVAV22998 for ; Thu, 13 Mar 2003 21:31:10 GMT Received: from io.frii.com (localhost.frii.com [127.0.0.1]) by io.frii.com (8.12.8/8.12.8) with ESMTP id h2DLVD6f066254 for ; Thu, 13 Mar 2003 14:31:13 -0700 (MST) Received: (from markzimm@localhost) by io.frii.com (8.12.8/8.12.8/Submit) id h2DLVD8t066253 for omninotify-list@omniorb-support.com; Thu, 13 Mar 2003 14:31:13 -0700 (MST) From: Mark Zimmerman To: omninotify-list@omniorb-support.com Message-ID: <20030313213112.GA66180@io.frii.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline User-Agent: Mutt/1.4i Subject: [omniNotify] omniORB 4.0.1, omniNotify 2.0 alpha, and AIX Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Thu Mar 13 21:32:01 2003 X-Original-Date: Thu, 13 Mar 2003 14:31:13 -0700 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings: OK, let's try this again _with_ the attachment... I am trying to compile omniNotify 2.0 alpha with omniORB 4.0.1 on an AIX machine. There are some problems with library dependencies that the attached patch seems to work around. I am sure that this is not the correct answer to the problem but it may be of informational value. The problems occur when linking libAttNotificationDynamic4.a.0 and libCOSDynamic4.a.0. Both have a multitude of unresolved externals that are resolved by adding a library to the link. This is not necessary under Solaris or Linux. Also, in both cases the following linker warnings are reported: ld: 0711-415 WARNING: Symbol __cdtors is already exported. ld: 0711-415 WARNING: Symbol __priority0x80000028 is already exported. -- Mark --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="omniNotify-aix.patch" Index: lib/dir.mk =================================================================== RCS file: /home/cvsroot/omniNotify/lib/dir.mk,v retrieving revision 1.32.4.1 diff -u -r1.32.4.1 dir.mk --- lib/dir.mk 21 May 2002 13:27:00 -0000 1.32.4.1 +++ lib/dir.mk 13 Mar 2003 19:42:20 -0000 @@ -93,7 +93,7 @@ mkshared:: $(skshared) $(skshared): $(patsubst %, shared/%, $(NFYLIB_OBJS)) - @(namespec="$(sknamespec)" extralibs="$(OMNIORB_LIB) $(COS_LIB)"; \ + @(namespec="$(sknamespec)" extralibs="$(OMNIORB_LIB) $(COS_LIB) -lAttNotification40"; \ $(MakeCXXSharedLibrary)) export:: $(skshared) Index: mkattlib/dir.mk =================================================================== RCS file: /home/cvsroot/omniNotify/mkattlib/dir.mk,v retrieving revision 1.1.10.2 diff -u -r1.1.10.2 dir.mk --- mkattlib/dir.mk 21 May 2002 20:40:25 -0000 1.1.10.2 +++ mkattlib/dir.mk 13 Mar 2003 19:42:20 -0000 @@ -89,7 +89,7 @@ imps := $(patsubst $(DLLDebugSearchPattern),$(DLLNoDebugSearchPattern), \ $(OMNIORB_LIB)) else -imps := $(OMNIORB_LIB) +imps := $(OMNIORB_LIB) -lCOSDynamic40 endif --Q68bSM7Ycu6FN28Q-- From plvaugh@sandia.gov Wed Mar 26 17:01:41 2003 Received: from mm02snlnto.son.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21]) by raq2100.uk2net.com (8.10.2/8.10.2) with ESMTP id h2QH1e108833 for ; Wed, 26 Mar 2003 17:01:40 GMT Received: from 132.175.109.1 by MM01SNLNTO.sandia.gov with ESMTP ( Tumbleweed MMS SMTP Relay 01 (MMS v5.5.0)); Wed, 26 Mar 2003 10:01:35 -0600 Received: from sandia.gov (samt5475.sandia.gov [134.253.236.172]) by sass165.sandia.gov (8.12.8/8.12.8) with ESMTP id h2QH1WQ2016551 for ; Wed, 26 Mar 2003 10:01:32 -0700 (MST) MIME-Version: 1.0 From: "Patrick Vaughan" To: omninotify-list@omniorb-support.com Message-ID: <9996CFA6-5FAC-11D7-BF5E-003065F93D8E@sandia.gov> X-Mailer: Apple Mail (2.551) X-WSS-ID: 129F0365699804-01-01 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [omniNotify] Problem trying to _narrow an omniNotify Channel Sender: omninotify-list-admin@omniorb-support.com Errors-To: omninotify-list-admin@omniorb-support.com X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: Date: Wed Mar 26 17:02:01 2003 X-Original-Date: Wed, 26 Mar 2003 10:01:34 -0700 Hi, I'm trying to use omniNotify from Python. When I try to _narrow a channel object, the program just hangs. I don't get any error messages and no exceptions are thrown. Any suggestions on what might be wrong would be greatly appreciated. I'm using omniORB 4.0.0 omniORBpy 2.0 and omniNotify 2.0 alpha. Thanks, Pat try: channelName = "ChannelFactory" name = [CosNaming.NameComponent(channelName, channelName)] channelObj = nameContext.resolve(name) channel = channelObj._narrow(CosNotifyChannelAdmin.EventChannelFactory) # <- hangs here except: print "Error" From Cameron.Rochester@Ripple-Systems.com Wed May 28 10:24:36 2003 Received: from [203.17.161.11] (helo=webmailme.motherwell.com.au) by omniorb-support.com with smtp (Exim 4.14) id 19KxAh-00069O-MR for omninotify-list@omniorb-support.com; Wed, 28 May 2003 10:24:36 +0100 Received: (qmail 8457 invoked by uid 1007); 28 May 2003 09:13:00 -0000 Received: from Cameron.Rochester@Ripple-Systems.com by webmailme by uid 1004 with qmail-scanner-1.15 (uvscan: v4.1.60/v4266. Clear:. Processed in 2.540557 secs); 28 May 2003 09:13:00 -0000 Received: from unknown (HELO envelope.pth.motherwell.com.au) (192.168.70.14) by webmailme.motherwell.com.au with SMTP; 28 May 2003 09:12:56 -0000 Received: by envelope.pth.motherwell.com.au with Internet Mail Service (5.5.2653.19) id ; Wed, 28 May 2003 17:12:56 +0800 Message-ID: From: Cameron Rochester To: omninotify-list@omniorb-support.com Subject: [omniNotify] Filter Evaluation Problems Date: Wed, 28 May 2003 17:12:52 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 09:24:36 -0000 Hi all, I am having some problems with omniNotify 2.0. It does not seem to evaluate my filters correctly - either that or I don't know how to use it... --- I am sending events of the following --- // // Fixed Header // event->header.fixed_header.event_type.domain_name = CORBA::string_dup( "Foo" ); event->header.fixed_header.event_type.type_name = CORBA::string_dup( "Bar" ); // // Filterable Data // event->filterable_data.length( 1 ); event->filterable_data[0].name = CORBA::string_dup( "Name" ); event->filterable_data[0].value <<= "Value"; --- I create a subscriber with the following Filter attached to the proxy --- CosNotification::EventTypeSeq seq; seq.length(1); seq[0].domain_name = "Foo"; seq[0].type_name = "Bar"; CosNotifyFilter::ConstraintExpSeq expression; expression.length(1); expression[0].event_types = seq; expression[0].constraint_expr = "( $.header.filterable_data(Name) == 'Value' )"; --- I have also tried to no avail --- // this expression[0].constraint_expr = "$.header.filterable_data(Name) == 'Value' "; // or expression[0].constraint_expr = "( $.Name) == 'Value' )"; //or expression[0].constraint_expr = "$.Name == 'Value' "; --- Now, I have been using the TAO Notification Service up to now without any problems with these constraints. (Took me a while to figure out a number of the differences between omniNotify & TAO - such as filters correctly implementing attach_callback for subscription_change notifications in omniNotify) If I *don't* specify the constraint (ie: set it to 'true') and still specify the domain_name and type_name, I receive the events just fine.... I have tried turning on the debug options in the omniNotify configuration file but I don't seem to get any output to either stderr or to a log file (the log file is created, it just isn't populated) Any ideas - should the above constraint work? Cheers Cameron From gruber@research.att.com Wed May 28 14:16:39 2003 Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com) by omniorb-support.com with esmtp (Exim 4.14) id 19L0nH-0006eA-DA for omninotify-list@omniorb-support.com; Wed, 28 May 2003 14:16:39 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h4SD0B3j004250; Wed, 28 May 2003 09:00:11 -0400 Received: from pcgruberhome (brow2116.research.att.com [135.207.58.116]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with SMTP id h4SD4WV02340; Wed, 28 May 2003 09:04:32 -0400 (EDT) Message-ID: <001301c32519$ae57b6e0$743acf87@research.att.com> From: "Robert E. Gruber" To: "Cameron Rochester" , References: Subject: Re: [omniNotify] Filter Evaluation Problems Date: Wed, 28 May 2003 09:04:31 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: "Robert E. Gruber" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 13:16:39 -0000 If you send me your supplier/consumer code I will try it out and see what is happening. BTW you could also write $Name == 'Value' for the constraint expression. -- Bob ----- Original Message ----- From: "Cameron Rochester" To: Sent: Wednesday, May 28, 2003 5:12 AM Subject: [omniNotify] Filter Evaluation Problems > Hi all, > > I am having some problems with omniNotify 2.0. It does not seem to evaluate > my filters correctly - either that or I don't know how to use it... > > --- I am sending events of the following --- > > // > // Fixed Header > // > event->header.fixed_header.event_type.domain_name = CORBA::string_dup( "Foo" > ); > event->header.fixed_header.event_type.type_name = CORBA::string_dup( "Bar" > ); > > // > // Filterable Data > // > event->filterable_data.length( 1 ); > event->filterable_data[0].name = CORBA::string_dup( "Name" ); > event->filterable_data[0].value <<= "Value"; > > > --- I create a subscriber with the following Filter attached to the proxy > --- > > CosNotification::EventTypeSeq seq; > seq.length(1); > seq[0].domain_name = "Foo"; > seq[0].type_name = "Bar"; > > CosNotifyFilter::ConstraintExpSeq expression; > expression.length(1); > expression[0].event_types = seq; > expression[0].constraint_expr = "( $.header.filterable_data(Name) == 'Value' > )"; > > --- I have also tried to no avail --- > // this > expression[0].constraint_expr = "$.header.filterable_data(Name) == 'Value' > "; > // or > expression[0].constraint_expr = "( $.Name) == 'Value' )"; > //or > expression[0].constraint_expr = "$.Name == 'Value' "; > > --- > > Now, I have been using the TAO Notification Service up to now without any > problems with these constraints. (Took me a while to figure out a number of > the differences between omniNotify & TAO - such as filters correctly > implementing attach_callback for subscription_change notifications in > omniNotify) > > If I *don't* specify the constraint (ie: set it to 'true') and still specify > the domain_name and type_name, I receive the events just fine.... > > I have tried turning on the debug options in the omniNotify configuration > file but I don't seem to get any output to either stderr or to a log file > (the log file is created, it just isn't populated) > > Any ideas - should the above constraint work? > > Cheers > Cameron > > > > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > From Cameron.Rochester@Ripple-Systems.com Thu May 29 01:41:26 2003 Received: from [203.17.161.11] (helo=webmailme.motherwell.com.au) by omniorb-support.com with smtp (Exim 4.14) id 19LBTy-0007Hq-02 for omninotify-list@omniorb-support.com; Thu, 29 May 2003 01:41:26 +0100 Received: (qmail 17207 invoked by uid 1007); 29 May 2003 00:29:23 -0000 Received: from Cameron.Rochester@Ripple-Systems.com by webmailme by uid 1004 with qmail-scanner-1.15 (uvscan: v4.1.60/v4267. Clear:. Processed in 2.578357 secs); 29 May 2003 00:29:23 -0000 Received: from unknown (HELO envelope.pth.motherwell.com.au) (192.168.70.14) by webmailme.motherwell.com.au with SMTP; 29 May 2003 00:29:19 -0000 Received: by envelope.pth.motherwell.com.au with Internet Mail Service (5.5.2653.19) id ; Thu, 29 May 2003 08:29:18 +0800 Message-ID: From: Cameron Rochester To: omninotify-list@omniorb-support.com Subject: RE: [omniNotify] Filter Evaluation Problems Date: Thu, 29 May 2003 08:29:16 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2003 00:41:26 -0000 No need to send you the code :) $Name == 'Value' worked. It is a bit concerning that $.Name == 'Value' does not work as this is an acceptable constraint as defined by the OMG spec. I hope that the $Name == 'Value' syntax works with the TAO Notification service :) Cheers! Cameron -----Original Message----- From: Robert E. Gruber [mailto:gruber@research.att.com] Sent: Wednesday, May 28, 2003 9:05 PM To: Cameron Rochester; omninotify-list@omniorb-support.com Cc: Robert E. Gruber Subject: Re: [omniNotify] Filter Evaluation Problems If you send me your supplier/consumer code I will try it out and see what is happening. BTW you could also write $Name == 'Value' for the constraint expression. -- Bob ----- Original Message ----- From: "Cameron Rochester" To: Sent: Wednesday, May 28, 2003 5:12 AM Subject: [omniNotify] Filter Evaluation Problems > Hi all, > > I am having some problems with omniNotify 2.0. It does not seem to evaluate > my filters correctly - either that or I don't know how to use it... > > --- I am sending events of the following --- > > // > // Fixed Header > // > event->header.fixed_header.event_type.domain_name = CORBA::string_dup( "Foo" > ); > event->header.fixed_header.event_type.type_name = CORBA::string_dup( "Bar" > ); > > // > // Filterable Data > // > event->filterable_data.length( 1 ); > event->filterable_data[0].name = CORBA::string_dup( "Name" ); > event->filterable_data[0].value <<= "Value"; > > > --- I create a subscriber with the following Filter attached to the proxy > --- > > CosNotification::EventTypeSeq seq; > seq.length(1); > seq[0].domain_name = "Foo"; > seq[0].type_name = "Bar"; > > CosNotifyFilter::ConstraintExpSeq expression; > expression.length(1); > expression[0].event_types = seq; > expression[0].constraint_expr = "( $.header.filterable_data(Name) == 'Value' > )"; > > --- I have also tried to no avail --- > // this > expression[0].constraint_expr = "$.header.filterable_data(Name) == 'Value' > "; > // or > expression[0].constraint_expr = "( $.Name) == 'Value' )"; > //or > expression[0].constraint_expr = "$.Name == 'Value' "; > > --- > > Now, I have been using the TAO Notification Service up to now without any > problems with these constraints. (Took me a while to figure out a number of > the differences between omniNotify & TAO - such as filters correctly > implementing attach_callback for subscription_change notifications in > omniNotify) > > If I *don't* specify the constraint (ie: set it to 'true') and still specify > the domain_name and type_name, I receive the events just fine.... > > I have tried turning on the debug options in the omniNotify configuration > file but I don't seem to get any output to either stderr or to a log file > (the log file is created, it just isn't populated) > > Any ideas - should the above constraint work? > > Cheers > Cameron > > > > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > From jon@totient.demon.co.uk Sun Jun 08 22:05:35 2003 Received: from anchor-post-39.mail.demon.net ([194.217.242.80]) by omniorb-support.com with esmtp (Exim 4.14) id 19P7M7-0005mf-9H for omninotify-list@omniorb-support.com; Sun, 08 Jun 2003 22:05:35 +0100 Received: from totient.demon.co.uk ([80.177.108.44]) by anchor-post-39.mail.demon.net with esmtp (Exim 3.36 #2) id 19P75L-0004xg-0U for omninotify-list@omniorb-support.com; Sun, 08 Jun 2003 21:48:15 +0100 Content-Type: text/plain; charset="us-ascii" From: Jon Dyte To: omninotify-list@omniorb-support.com Date: Sun, 8 Jun 2003 21:51:02 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200306082151.02263.jon@totient.demon.co.uk> Subject: [omniNotify] python versions of the omniNotify example programs X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2003 21:05:35 -0000 Hi The title says it all really. Do these exist? I'm sure I have seen refere= nce=20 mad to python version of any_push_supplier etc, using omniORBpy, however, these dont seem to be in CVS. I've written a version of any_push_supplier in python , which needs some refactoring to become a module for all the other examples, but before I g= o ahead and do this, I dont want to reinvent the wheel if these exist alrea= dy. do the python versions already exist? regards, jon =20 From markzimm@io.frii.com Wed Jun 18 17:47:46 2003 Received: from io.frii.com ([216.17.222.1]) by omniorb-support.com with esmtp (Exim 4.14) id 19Sg66-0003ks-EN for omninotify-list@omniorb-support.com; Wed, 18 Jun 2003 17:47:46 +0100 Received: from io.frii.com (localhost.frii.com [127.0.0.1]) by io.frii.com (8.12.9/8.12.9) with ESMTP id h5IGPYur069560 for ; Wed, 18 Jun 2003 10:25:37 -0600 (MDT) Received: (from markzimm@localhost) by io.frii.com (8.12.9/8.12.9/Submit) id h5IGPW1a069559 for omninotify-list@omniorb-support.com; Wed, 18 Jun 2003 10:25:32 -0600 (MDT) Date: Wed, 18 Jun 2003 10:25:32 -0600 From: Mark Zimmerman To: omninotify-list@omniorb-support.com Message-ID: <20030618162532.GA69351@io.frii.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: [omniNotify] omniNotify 2.0 X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 16:47:46 -0000 Greetings: omniNotify 2.0 has been working well for me for quite a long time now. Are there any plans to declare success and remove the alpha designation? -- Mark From gruber@research.att.com Wed Jun 18 18:34:56 2003 Received: from h-135-207-24-16.research.att.com ([135.207.24.16] helo=linux.research.att.com) by omniorb-support.com with esmtp (Exim 4.14) id 19Sgpk-0003nm-LD for omninotify-list@omniorb-support.com; Wed, 18 Jun 2003 18:34:56 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h5IHJjEI016017; Wed, 18 Jun 2003 13:19:45 -0400 Received: from pcgruber (pc-gruber.research.att.com [135.207.23.156]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h5IHCFV02340; Wed, 18 Jun 2003 13:12:15 -0400 (EDT) From: "Robert E. Gruber" To: "'Mark Zimmerman'" , Subject: RE: [omniNotify] omniNotify 2.0 Date: Wed, 18 Jun 2003 13:10:03 -0400 Message-ID: <01a501c335bc$7595a110$9c17cf87@pcgruber> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 In-Reply-To: <20030618162532.GA69351@io.frii.com> Importance: Normal Cc: "Robert E. Gruber" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 17:34:56 -0000 Yes, it will happen! But a couple things have been holding me back. Duncan has set up a sourceforge CVS repository, and this will become the official omniNotify CVS repository as soon as I get the time to update a few things. (Thanks Duncan!) I believe Duncan also has autoconf working for omniNotify, and I'd like to include that support in the 2.0 release. And there are a few fixes that should also go in, including fixing a case where a lock is held across a push call, something the channel should never do. So yes it will happen, and I hope it will be soon. But probably not this week :-> Thanks for you patience, -- Bob -----Original Message----- From: omninotify-list-bounces@omniorb-support.com [mailto:omninotify-list-bounces@omniorb-support.com] On Behalf Of Mark Zimmerman Sent: Wednesday, June 18, 2003 12:26 PM To: omninotify-list@omniorb-support.com Subject: [omniNotify] omniNotify 2.0 Greetings: omniNotify 2.0 has been working well for me for quite a long time now. Are there any plans to declare success and remove the alpha designation? -- Mark _______________________________________________ omninotify-list mailing list omninotify-list@omniorb-support.com http://www.omniorb-support.com/mailman/listinfo/omninotify-list From duncan@grisby.org Thu Jun 19 18:03:48 2003 Received: from pc2-cmbg4-5-cust210.cmbg.cable.ntl.com ([81.96.73.210] helo=grisby.dyndns.org) by omniorb-support.com with esmtp (Exim 4.14) id 19T2p9-0005Y2-Sb for omninotify-list@omniorb-support.com; Thu, 19 Jun 2003 18:03:47 +0100 Received: from grisby.org (dpg1@localhost) by grisby.dyndns.org (8.11.6/8.11.6) with ESMTP id h5JGf8X25880 for ; Thu, 19 Jun 2003 17:41:08 +0100 Message-Id: <200306191641.h5JGf8X25880@grisby.dyndns.org> X-Authentication-Warning: pc2-cmbg4-5-cust210.cmbg.cable.ntl.com: dpg1 owned process doing -bs To: omninotify-list@omniorb-support.com Subject: Re: [omniNotify] omniNotify 2.0 In-Reply-To: Message from "Robert E. Gruber" of "Wed, 18 Jun 2003 13:10:03 EDT." <01a501c335bc$7595a110$9c17cf87@pcgruber> From: Duncan Grisby Date: Thu, 19 Jun 2003 17:41:08 +0100 X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2003 17:03:48 -0000 On Wednesday 18 June, "Robert E. Gruber" wrote: > I believe Duncan also has autoconf working for omniNotify, and I'd > like to include that support in the 2.0 release. Yes, autoconf is working, in the SourceForge CVS. I have also just checked in the changes to support omniNotify on Windows. Aside from the usual platform differences, I encountered some problems with the omniORB DLL handling, and a compiler bug in Visual C++. The result of that is that I've had to change some things about the IDL compiler output. To get omniNotify to work, you need to get the current CVS contents of omniORB, and do a clean build of that, before building omniNotify. I haven't completely tested the Windows port yet, so there may still be problems with it. The examples all seem to work ok. Cheers, Duncan. -- -- Duncan Grisby -- -- duncan@grisby.org -- -- http://www.grisby.org -- From Cameron.Rochester@Ripple-Systems.com Tue Jun 24 07:54:12 2003 Received: from [203.17.161.11] (helo=webmailme.motherwell.com.au) by omniorb-support.com with smtp (Exim 4.14) id 19Uhgx-0003t0-Le for omninotify-list@omniorb-support.com; Tue, 24 Jun 2003 07:54:12 +0100 Received: (qmail 16763 invoked by uid 1007); 24 Jun 2003 06:29:10 -0000 Received: from Cameron.Rochester@Ripple-Systems.com by webmailme by uid 1004 with qmail-scanner-1.15 (uvscan: v4.1.60/v4272. Clear:. Processed in 2.549699 secs); 24 Jun 2003 06:29:10 -0000 Received: from unknown (HELO envelope.pth.motherwell.com.au) (192.168.70.14) by webmailme.motherwell.com.au with SMTP; 24 Jun 2003 06:29:06 -0000 Received: by envelope.pth.motherwell.com.au with Internet Mail Service (5.5.2653.19) id ; Tue, 24 Jun 2003 14:29:06 +0800 Message-ID: From: Cameron Rochester To: "'omninotify-list@omniorb-support.com'" Subject: [omniNotify] Win32 dll's Date: Tue, 24 Jun 2003 14:29:05 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 06:54:12 -0000 Hi all, Given that there is nothing new under the sun - I was wondering if anyone has compiled some release libraries and DLLs for omniNotify 2.0 Alpha (with omniORB 4.0.1) under win32 (NT/2k)? I would need the AttNotification, and libCOSNotify4 dlls (and placeholder libs of course ;). If so, could you please post a link to a zip, or similar, that I could download? I will be eternally grateful! :) Regards Cameron Rochester From goetz@esrf.fr Tue Jun 24 08:05:26 2003 Received: from firewall.sfn.asso.fr ([193.49.43.1] helo=out.esrf.fr) by omniorb-support.com with esmtp (Exim 4.14) id 19Uhrq-0003vH-6v for omninotify-list@omniorb-support.com; Tue, 24 Jun 2003 08:05:26 +0100 Received: (from uucp@localhost) by out.esrf.fr (1.0.0) id h5O6dm816953; Tue, 24 Jun 2003 08:39:48 +0200 (MEST) Received: from esrf.esrf.fr(160.103.2.9) by firewall via smap (V1.3) id tmp016770; Tue Jun 24 08:39:28 2003 Subject: Re: [omniNotify] Win32 dll's Received: from starwars.esrf.fr (localhost [127.0.0.1]) by esrf.esrf.fr (8.9.0/8.9.0) with ESMTP id IAA19224; Tue, 24 Jun 2003 08:39:27 +0200 (MET DST) Received: from localhost (goetz@localhost) by starwars.esrf.fr (8.11.6+Sun/8.11.6) with ESMTP id h5O6dQe05667; Tue, 24 Jun 2003 08:39:26 +0200 (MEST) X-Authentication-Warning: starwars.esrf.fr: goetz owned process doing -bs Date: Tue, 24 Jun 2003 08:39:26 +0200 (MEST) From: Andy Goetz To: Cameron Rochester In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "'omninotify-list@omniorb-support.com'" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 07:05:26 -0000 Hi, I am busy going thru this exercise but fighting with my Visual C++ installation under Win 98. Maybe Duncan can provide us with a ready compiled version ;-) Otherwise I hope to do this under Win2k. I will send you my result as soon as I have something. Andy On Tue, 24 Jun 2003, Cameron Rochester wrote: > Hi all, > > Given that there is nothing new under the sun - I was wondering if anyone > has compiled some release libraries and DLLs for omniNotify 2.0 Alpha (with > omniORB 4.0.1) under win32 (NT/2k)? I would need the AttNotification, and > libCOSNotify4 dlls (and placeholder libs of course ;). > > If so, could you please post a link to a zip, or similar, that I could > download? I will be eternally grateful! :) > > Regards > Cameron Rochester > > _______________________________________________ > omninotify-list mailing list > omninotify-list@omniorb-support.com > http://www.omniorb-support.com/mailman/listinfo/omninotify-list > -- European Synchrotron Radiation Facility 6, rue Jules Horowitz, Grenoble, 38043 FRANCE tel: (+33)-476882646 email: goetz@esrf.fr andy_gotz@yahoo.fr From gruber@research.att.com Thu Jul 03 15:36:01 2003 Received: from h-135-207-24-16.research.att.com ([135.207.24.16] helo=linux.research.att.com) by omniorb-support.com with esmtp (Exim 4.14) id 19Y5Bp-00021J-61 for omninotify-list@omniorb-support.com; Thu, 03 Jul 2003 15:36:01 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h63EHWJh027769 for ; Thu, 3 Jul 2003 10:17:32 -0400 Received: from pcgruberhome (brow2116.research.att.com [135.207.58.116]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with SMTP id h63E5tV13486; Thu, 3 Jul 2003 10:05:55 -0400 (EDT) Message-ID: <009a01c3416c$38787e40$743acf87@research.att.com> From: "Robert E. Gruber" To: Date: Thu, 3 Jul 2003 10:05:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: "Robert E. Gruber" Subject: [omniNotify] latest omniNotify2_alpha is in sourceforge X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2003 14:36:01 -0000 The omniNotify CVS repository has moved to sourceforge. You can get the lates omniNotify2_alpha there. anonymous access has been a problem lately... Duncan, would you mind making sure the latest snapshot is up to date and telling people how to get things that way? I just checked in changes that include some bug fixes. I would appreciate it if a few people would try things out. Unfortunately I will be away today through July 13, so I will not be able to help or work on fixes until then but I would appreciate it if some people had tried things by the time I return. Many thanks!! -- Bob Gruber From duncan@grisby.org Thu Jul 03 16:45:26 2003 Received: from pc2-cmbg4-5-cust210.cmbg.cable.ntl.com ([81.96.73.210] helo=grisby.dyndns.org) by omniorb-support.com with esmtp (Exim 4.14) id 19Y6H0-0002Yc-31 for omninotify-list@omniorb-support.com; Thu, 03 Jul 2003 16:45:26 +0100 Received: from grisby.org (dpg1@localhost) by grisby.dyndns.org (8.11.6/8.11.6) with ESMTP id h63FFnc32052 for ; Thu, 3 Jul 2003 16:15:49 +0100 Message-Id: <200307031515.h63FFnc32052@grisby.dyndns.org> X-Authentication-Warning: pc2-cmbg4-5-cust210.cmbg.cable.ntl.com: dpg1 owned process doing -bs To: omninotify-list@omniorb-support.com Subject: Re: [omniNotify] latest omniNotify2_alpha is in sourceforge In-Reply-To: Message from "Robert E. Gruber" of "Thu, 03 Jul 2003 10:05:47 EDT." <009a01c3416c$38787e40$743acf87@research.att.com> From: Duncan Grisby Date: Thu, 03 Jul 2003 16:15:49 +0100 X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2003 15:45:26 -0000 On Thursday 3 July, "Robert E. Gruber" wrote: > The omniNotify CVS repository has moved to sourceforge. > You can get the lates omniNotify2_alpha there. anonymous > access has been a problem lately... Duncan, would you mind > making sure the latest snapshot is up to date and telling people > how to get things that way? The CVS page with instructions about getting it from anonymous CVS is here: http://sourceforge.net/cvs/?group_id=77499 As Bob says, anonymous access has been flaky recently. Instead, you can get a snapshot of a checkout from http://omniorb.sourceforge.net/snapshots/ Note that for omniNotify to work on Windows, you must use the CVS version of omniORB, since there are some changes in that to support it. Cheers, Duncan. -- -- Duncan Grisby -- -- duncan@grisby.org -- -- http://www.grisby.org -- From markzimm@io.frii.com Wed Jul 16 15:50:38 2003 Received: from io.frii.com ([216.17.222.1]) by omniorb-support.com with esmtp (Exim 4.14) id 19cnc6-0006xT-I2 for omninotify-list@omniorb-support.com; Wed, 16 Jul 2003 15:50:38 +0100 Received: from io.frii.com (localhost.frii.com [127.0.0.1]) by io.frii.com (8.12.9/8.12.9) with ESMTP id h6GEEWIg061113; Wed, 16 Jul 2003 08:14:33 -0600 (MDT) Received: (from markzimm@localhost) by io.frii.com (8.12.9/8.12.9/Submit) id h6GEEUs3061112; Wed, 16 Jul 2003 08:14:30 -0600 (MDT) Date: Wed, 16 Jul 2003 08:14:30 -0600 From: Mark Zimmerman To: "Robert E. Gruber" , omninotify-list@omniorb-support.com Subject: Re: [omniNotify] latest omniNotify2_alpha is in sourceforge Message-ID: <20030716141430.GA60674@io.frii.com> References: <009a01c3416c$38787e40$743acf87@research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <009a01c3416c$38787e40$743acf87@research.att.com> User-Agent: Mutt/1.4.1i Cc: X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 14:50:38 -0000 On Thu, Jul 03, 2003 at 10:05:47AM -0400, Robert E. Gruber wrote: > The omniNotify CVS repository has moved to sourceforge. > You can get the lates omniNotify2_alpha there. anonymous > access has been a problem lately... Duncan, would you mind > making sure the latest snapshot is up to date and telling people > how to get things that way? > > I just checked in changes that include some bug fixes. > I would appreciate it if a few people would try things out. > Unfortunately I will be away today through July 13, so I > will not be able to help or work on fixes until then but I > would appreciate it if some people had tried things by the > time I return. > FYI, I downloaded the 03 July snapshots and successfully built with autoconf on Solaris 7 and 8 and on AIX 4.3 (xlC). The AIX build required some patching but it has been working fine. Solaris works as-is. -- Mark From gruber@research.att.com Wed Jul 16 16:19:45 2003 Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com) by omniorb-support.com with esmtp (Exim 4.14) id 19co4G-00070x-VQ for omninotify-list@omniorb-support.com; Wed, 16 Jul 2003 16:19:45 +0100 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h6GEZf3j027831; Wed, 16 Jul 2003 10:35:41 -0400 Received: from pcgruberhome (brow2116.research.att.com [135.207.58.116]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with SMTP id h6GEh8V17037; Wed, 16 Jul 2003 10:43:08 -0400 (EDT) Message-ID: <003301c34ba8$9309fc80$743acf87@research.att.com> From: "Robert E. Gruber" To: "Mark Zimmerman" , References: <009a01c3416c$38787e40$743acf87@research.att.com> <20030716141430.GA60674@io.frii.com> Subject: Re: [omniNotify] latest omniNotify2_alpha is in sourceforge Date: Wed, 16 Jul 2003 10:43:08 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: "Robert E. Gruber" X-BeenThere: omninotify-list@omniorb-support.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: The omniNotify Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 15:19:45 -0000 Mark, thanks for checking things out. Please send me the AIX changes so I can add them in. -- Bob ----- Original Message ----- From: "Mark Zimmerman" To: "Robert E. Gruber" ; Sent: Wednesday, July 16, 2003 10:14 AM Subject: Re: [omniNotify] latest omniNotify2_alpha is in sourceforge > On Thu, Jul 03, 2003 at 10:05:47AM -0400, Robert E. Gruber wrote: > > The omniNotify CVS repository has moved to sourceforge. > > You can get the lates omniNotify2_alpha there. anonymous > > access has been a problem lately... Duncan, would you mind > > making sure the latest snapshot is up to date and telling people > > how to get things that way? > > > > I just checked in changes that include some bug fixes. > > I would appreciate it if a few people would try things out. > > Unfortunately I will be away today through July 13, so I > > will not be able to help or work o