Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Java Messaging Service

10 posts in General Discussion (old) Last posting was on 2000-03-20 21:32:38.0Z
Basant Gupta Posted on 2000-03-17 06:11:46.0Z
Newsgroups: sybase.public.easerver
Date: Thu, 16 Mar 2000 22:11:46 -0800
From: Basant Gupta <basantg@yahoo.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.71 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 18
NNTP-Posting-Host: robocop-5-pool22.sybase.com 130.214.144.151
Message-ID: <347_38D1CCA2.A27D53CC@yahoo.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26232
Article PK: 156901

Hi,
I'm not sure which release of EAServer is supposed to support the
the Java Messaging Service (JMS). I need some clarification about this
service.

Is this service going to be available only to Java components in
EAServer? Or will this service be able to be accessed by any type of
components (PB, C++, etc), much like the CosNaming Service or the
Transaction Management Service ?

I am currently building an application (PB server components) which
requires asynchronous messaging. The way I currently handle this is
through polling. I am wondering if my PB components could benefit from
the JMS service once it is implemented in EAServer.

Regards,
Basant Gupta


Scott McReynolds [Sybase] Posted on 2000-03-17 15:44:49.0Z
Newsgroups: sybase.public.easerver
From: "Scott McReynolds [Sybase]" <scottmc@sybase.com>
Subject: Re: Java Messaging Service
Date: Fri, 17 Mar 2000 08:44:49 -0700
Lines: 49
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: scottmc-lpt.sybase.com 157.133.56.40
Message-ID: <347_xwHjPhCk$GA.261@forums.sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26199
Article PK: 156869

Basant,

This will be avalible with 3.6 at the latest. It may be avalible as an EBF,
but we are still looking into that option at this point. Here is a
description of the message service:

The message service provides queues for message consumers, and allows a
message producers to send messages to specified queues (point-to-point
messaging), or to publish messages with specified topics that may be of
interest to registered consumers (publish/subscribe messaging).

Messages that are sent or published to a queue are stored in memory
(transient messages) or in a database (persistent messages) until they can
be delivered to the queue's consumer, which is either a client or a
component. The message service provides a pull-style mechanism for client
notification, and a push-style mechanism for component notification.

Once configuration is complete, the message service can be accessed by CORBA
2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface, or by
Java/EJB clients using the Java Message Service (JMS) API.

Hope this helps.
Scott

"Basant Gupta" <basantg@yahoo.com> wrote in message
news:38D1CCA2.A27D53CC@yahoo.com...
> Hi,
> I'm not sure which release of EAServer is supposed to support the
> the Java Messaging Service (JMS). I need some clarification about this
> service.
>
> Is this service going to be available only to Java components in
> EAServer? Or will this service be able to be accessed by any type of
> components (PB, C++, etc), much like the CosNaming Service or the
> Transaction Management Service ?
>
> I am currently building an application (PB server components) which
> requires asynchronous messaging. The way I currently handle this is
> through polling. I am wondering if my PB components could benefit from
> the JMS service once it is implemented in EAServer.
>
> Regards,
> Basant Gupta
>
>


Basant Gupta Posted on 2000-03-17 17:06:30.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 17 Mar 2000 09:06:30 -0800
From: Basant Gupta <basantg@yahoo.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: scottmc@sybase.com
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 75
NNTP-Posting-Host: 207.171.209.94
Message-ID: <347_38D26616.76C30093@yahoo.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26190
Article PK: 156858

Hi Scott,
Thanks for your clarification. JMS certainly looks promising. Could you
provide a little more insight into the following questions.

1) From your message, "The message service provides a pull-style mechanism for
client notification, and a push-style mechanism for component notification.".
Does this mean that the client has to do some sort of polling. As for the
component, does this mean that we can pass component objects by reference ?
2) "Once configuration is complete, the message service can be accessed by CORBA
2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.". Would
PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?
3) This is really far-fetched but is there anyway in which HTML clients could
benefit from this messaging service through components in EAServer invoked by
PowerDynamo or through servelets ?

Regards,
Basant Gupta

"Scott McReynolds [Sybase]" wrote:

> Basant,
>
> This will be avalible with 3.6 at the latest. It may be avalible as an EBF,
> but we are still looking into that option at this point. Here is a
> description of the message service:
>
> The message service provides queues for message consumers, and allows a
> message producers to send messages to specified queues (point-to-point
> messaging), or to publish messages with specified topics that may be of
> interest to registered consumers (publish/subscribe messaging).
>
> Messages that are sent or published to a queue are stored in memory
> (transient messages) or in a database (persistent messages) until they can
> be delivered to the queue's consumer, which is either a client or a
> component. The message service provides a pull-style mechanism for client
> notification, and a push-style mechanism for component notification.
>
> Once configuration is complete, the message service can be accessed by CORBA
> 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface, or by
> Java/EJB clients using the Java Message Service (JMS) API.
>
> Hope this helps.
> Scott
>
> "Basant Gupta" <basantg@yahoo.com> wrote in message
> news:38D1CCA2.A27D53CC@yahoo.com...
> > Hi,
> > I'm not sure which release of EAServer is supposed to support the
> > the Java Messaging Service (JMS). I need some clarification about this
> > service.
> >
> > Is this service going to be available only to Java components in
> > EAServer? Or will this service be able to be accessed by any type of
> > components (PB, C++, etc), much like the CosNaming Service or the
> > Transaction Management Service ?
> >
> > I am currently building an application (PB server components) which
> > requires asynchronous messaging. The way I currently handle this is
> > through polling. I am wondering if my PB components could benefit from
> > the JMS service once it is implemented in EAServer.
> >
> > Regards,
> > Basant Gupta
> >
> >


Scott McReynolds [Sybase] Posted on 2000-03-17 18:55:12.0Z
Newsgroups: sybase.public.easerver
From: "Scott McReynolds [Sybase]" <scottmc@sybase.com>
Subject: Re: Java Messaging Service
Date: Fri, 17 Mar 2000 11:55:12 -0700
Lines: 108
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: scottmc-lpt.sybase.com 157.133.56.40
Message-ID: <347_30rZoLEk$GA.261@forums.sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D26616.76C30093@yahoo.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26177
Article PK: 154391

Basant,

See answers below.

Scott

"Basant Gupta" <basantg@yahoo.com> wrote in message
news:38D26616.76C30093@yahoo.com...
> Hi Scott,
> Thanks for your clarification. JMS certainly looks promising. Could
you
> provide a little more insight into the following questions.
>
> 1) From your message, "The message service provides a pull-style mechanism
for
> client notification, and a push-style mechanism for component
notification.".
> Does this mean that the client has to do some sort of polling. As for the
> component, does this mean that we can pass component objects by reference

?

Yes, you would need to have the client poll for the noticiation of a
particular message to be sent. As for components my understanding to this
point is that a component can receive a message just like a client will. I
have not played with it enough to get a good feeling for other capablities.

> 2) "Once configuration is complete, the message service can be accessed by
CORBA
> 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.".
Would
> PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?

Yes PowerBuilder could be a client to the service.

> 3) This is really far-fetched but is there anyway in which HTML clients
could
> benefit from this messaging service through components in EAServer invoked
by
> PowerDynamo or through servelets ?

In this case the HTML client would use something servlets or Dynamo to put
message on the queue and to pull messages from the queue. I'm trying to
play with that right now.

>
> Regards,
> Basant Gupta
>
>
>
> "Scott McReynolds [Sybase]" wrote:
>
> > Basant,
> >
> > This will be avalible with 3.6 at the latest. It may be avalible as an
EBF,
> > but we are still looking into that option at this point. Here is a
> > description of the message service:
> >
> > The message service provides queues for message consumers, and allows a
> > message producers to send messages to specified queues (point-to-point
> > messaging), or to publish messages with specified topics that may be of
> > interest to registered consumers (publish/subscribe messaging).
> >
> > Messages that are sent or published to a queue are stored in memory
> > (transient messages) or in a database (persistent messages) until they
can
> > be delivered to the queue's consumer, which is either a client or a
> > component. The message service provides a pull-style mechanism for
client
> > notification, and a push-style mechanism for component notification.
> >
> > Once configuration is complete, the message service can be accessed by
CORBA
> > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface,
or by
> > Java/EJB clients using the Java Message Service (JMS) API.
> >
> > Hope this helps.
> > Scott
> >
> > "Basant Gupta" <basantg@yahoo.com> wrote in message
> > news:38D1CCA2.A27D53CC@yahoo.com...
> > > Hi,
> > > I'm not sure which release of EAServer is supposed to support the
> > > the Java Messaging Service (JMS). I need some clarification about
this
> > > service.
> > >
> > > Is this service going to be available only to Java components in
> > > EAServer? Or will this service be able to be accessed by any type of
> > > components (PB, C++, etc), much like the CosNaming Service or the
> > > Transaction Management Service ?
> > >
> > > I am currently building an application (PB server components)
which
> > > requires asynchronous messaging. The way I currently handle this is
> > > through polling. I am wondering if my PB components could benefit
from
> > > the JMS service once it is implemented in EAServer.
> > >
> > > Regards,
> > > Basant Gupta
> > >
> > >
>


Evan Ireland Posted on 2000-03-20 21:32:38.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 21 Mar 2000 09:32:38 +1200
From: Evan Ireland <eireland@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Basant Gupta <basantg@yahoo.com>
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 41
NNTP-Posting-Host: vpn-eme-048.sybase.com 130.214.8.48
Message-ID: <347_38D698F6.A1E2CA89@sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D26616.76C30093@yahoo.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26054
Article PK: 156059


Basant Gupta wrote:
>
> Hi Scott,
> Thanks for your clarification. JMS certainly looks promising. Could you
> provide a little more insight into the following questions.
>
> 1) From your message, "The message service provides a pull-style mechanism for
> client notification, and a push-style mechanism for component notification.".
> Does this mean that the client has to do some sort of polling. As for the
> component, does this mean that we can pass component objects by reference ?

Client-pull uses a blocking call, whereas polling uses a non-blocking
call.

> 2) "Once configuration is complete, the message service can be accessed by CORBA
> 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.". Would
> PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?

Yes, PowerBuilder will work for client and component notification
as soon as we resolve an open issue with marshalling of CORBA IDL
union types.

> 3) This is really far-fetched but is there anyway in which HTML clients could
> benefit from this messaging service through components in EAServer invoked by
> PowerDynamo or through servelets ?

Your HTML clients (via PowerDynamo or servlets) could send messages and return
to clients without having to wait for the message processing to complete. That
would give better client response time.
________________________________________________________________________________

Evan Ireland Sybase EAServer Engineering eireland@sybase.com
Wellington, New Zealand +64 4 934-5856


Basant Gupta Posted on 2000-03-17 17:07:08.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 17 Mar 2000 09:07:08 -0800
From: Basant Gupta <basantg@yahoo.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 75
NNTP-Posting-Host: 207.171.209.94
Message-ID: <347_38D2663C.6D85029F@yahoo.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26189
Article PK: 156861

Hi Scott,
Thanks for your clarification. JMS certainlylooks promising. Could you
provide a little more insight into the following questions.

1) From your message, "The message service provides a pull-style mechanism for
client notification, and a push-style mechanism for component notification.".
Does this mean that the client has to do some sort of polling. As for the
component, does this mean that we can pass component objects by reference ?
2) "Once configuration is complete, the message service can be accessed by CORBA
2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.". Would
PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?
3) This is really far-fetched but is there anyway in which HTML clients could
benefit from this messaging service through components in EAServer invoked by
PowerDynamo or through servelets ?

Regards,
Basant Gupta

"Scott McReynolds [Sybase]" wrote:

> Basant,
>
> This will be avalible with 3.6 at the latest. It may be avalible as an EBF,
> but we are still looking into that option at this point. Here is a
> description of the message service:
>
> The message service provides queues for message consumers, and allows a
> message producers to send messages to specified queues (point-to-point
> messaging), or to publish messages with specified topics that may be of
> interest to registered consumers (publish/subscribe messaging).
>
> Messages that are sent or published to a queue are stored in memory
> (transient messages) or in a database (persistent messages) until they can
> be delivered to the queue's consumer, which is either a client or a
> component. The message service provides a pull-style mechanism for client
> notification, and a push-style mechanism for component notification.
>
> Once configuration is complete, the message service can be accessed by CORBA
> 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface, or by
> Java/EJB clients using the Java Message Service (JMS) API.
>
> Hope this helps.
> Scott
>
> "Basant Gupta" <basantg@yahoo.com> wrote in message
> news:38D1CCA2.A27D53CC@yahoo.com...
> > Hi,
> > I'm not sure which release of EAServer is supposed to support the
> > the Java Messaging Service (JMS). I need some clarification about this
> > service.
> >
> > Is this service going to be available only to Java components in
> > EAServer? Or will this service be able to be accessed by any type of
> > components (PB, C++, etc), much like the CosNaming Service or the
> > Transaction Management Service ?
> >
> > I am currently building an application (PB server components) which
> > requires asynchronous messaging. The way I currently handle this is
> > through polling. I am wondering if my PB components could benefit from
> > the JMS service once it is implemented in EAServer.
> >
> > Regards,
> > Basant Gupta
> >
> >


Himagiri Mukkamala Posted on 2000-03-17 20:07:37.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 17 Mar 2000 12:07:37 -0800
From: Himagiri Mukkamala <himagiri@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 91
NNTP-Posting-Host: cyclones.sybase.com 130.214.20.34
Message-ID: <347_38D29089.16224B89@sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D2663C.6D85029F@yahoo.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26162
Article PK: 156839

1) It doenst have to poll, the api has a timeout and if set
to low value, then it would be the equivalent of polling.
If not the recieve call on a queue for a message would be a
blocking call, so ur not polling.
U dont have to pass object reference, u have to pass the
name of the component which has a method named onMessage in
it.

2) Yes

3) Servlets could act like anyother java clients

himagiri

Basant Gupta wrote:
>
> Hi Scott,
> Thanks for your clarification. JMS certainlylooks promising. Could you
> provide a little more insight into the following questions.
>
> 1) From your message, "The message service provides a pull-style mechanism for
> client notification, and a push-style mechanism for component notification.".
> Does this mean that the client has to do some sort of polling. As for the
> component, does this mean that we can pass component objects by reference ?
> 2) "Once configuration is complete, the message service can be accessed by CORBA
> 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.". Would
> PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?
> 3) This is really far-fetched but is there anyway in which HTML clients could
> benefit from this messaging service through components in EAServer invoked by
> PowerDynamo or through servelets ?
>
> Regards,
> Basant Gupta
>
> "Scott McReynolds [Sybase]" wrote:
>
> > Basant,
> >
> > This will be avalible with 3.6 at the latest. It may be avalible as an EBF,
> > but we are still looking into that option at this point. Here is a
> > description of the message service:
> >
> > The message service provides queues for message consumers, and allows a
> > message producers to send messages to specified queues (point-to-point
> > messaging), or to publish messages with specified topics that may be of
> > interest to registered consumers (publish/subscribe messaging).
> >
> > Messages that are sent or published to a queue are stored in memory
> > (transient messages) or in a database (persistent messages) until they can
> > be delivered to the queue's consumer, which is either a client or a
> > component. The message service provides a pull-style mechanism for client
> > notification, and a push-style mechanism for component notification.
> >
> > Once configuration is complete, the message service can be accessed by CORBA
> > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface, or by
> > Java/EJB clients using the Java Message Service (JMS) API.
> >
> > Hope this helps.
> > Scott
> >
> > "Basant Gupta" <basantg@yahoo.com> wrote in message
> > news:38D1CCA2.A27D53CC@yahoo.com...
> > > Hi,
> > > I'm not sure which release of EAServer is supposed to support the
> > > the Java Messaging Service (JMS). I need some clarification about this
> > > service.
> > >
> > > Is this service going to be available only to Java components in
> > > EAServer? Or will this service be able to be accessed by any type of
> > > components (PB, C++, etc), much like the CosNaming Service or the
> > > Transaction Management Service ?
> > >
> > > I am currently building an application (PB server components) which
> > > requires asynchronous messaging. The way I currently handle this is
> > > through polling. I am wondering if my PB components could benefit from
> > > the JMS service once it is implemented in EAServer.
> > >
> > > Regards,
> > > Basant Gupta
> > >
> > >

--
Himagiri Mukkamala - EA Server Engineering,
Sybase Inc., 510.922.5477


Dave Wolf [Sybase] Posted on 2000-03-19 07:49:53.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Java Messaging Service
Date: Sun, 19 Mar 2000 02:49:53 -0500
Lines: 123
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-010.sybase.com 130.214.8.10
Message-ID: <347_fzFcShXk$GA.111@forums.sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D2663C.6D85029F@yahoo.com> <347_38D29089.16224B89@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26122
Article PK: 156798

Please see the IDL documentation for the module EventSamples for our design
pattern to avoid polling the server. The basic idea is that the client
spawns a thread and that thread makes a synchornous method call recieve().
When the message is delivered receive() will return and the thread will call
to its parent.

This is NOT polling and handles many common issues with async event deliery
in distributed models.

Dave Wolf
Internet Applications Division

"Himagiri Mukkamala" <himagiri@sybase.com> wrote in message
news:38D29089.16224B89@sybase.com...
> 1) It doenst have to poll, the api has a timeout and if set
> to low value, then it would be the equivalent of polling.
> If not the recieve call on a queue for a message would be a
> blocking call, so ur not polling.
> U dont have to pass object reference, u have to pass the
> name of the component which has a method named onMessage in
> it.
>
> 2) Yes
>
> 3) Servlets could act like anyother java clients
>
> himagiri
>
> Basant Gupta wrote:
> >
> > Hi Scott,
> > Thanks for your clarification. JMS certainlylooks promising. Could
you
> > provide a little more insight into the following questions.
> >
> > 1) From your message, "The message service provides a pull-style
mechanism for
> > client notification, and a push-style mechanism for component
notification.".
> > Does this mean that the client has to do some sort of polling. As for
the
> > component, does this mean that we can pass component objects by
reference ?
> > 2) "Once configuration is complete, the message service can be accessed
by CORBA
> > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.".
Would
> > PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?
> > 3) This is really far-fetched but is there anyway in which HTML clients
could
> > benefit from this messaging service through components in EAServer
invoked by
> > PowerDynamo or through servelets ?
> >
> > Regards,
> > Basant Gupta
> >
> > "Scott McReynolds [Sybase]" wrote:
> >
> > > Basant,
> > >
> > > This will be avalible with 3.6 at the latest. It may be avalible as
an EBF,
> > > but we are still looking into that option at this point. Here is a
> > > description of the message service:
> > >
> > > The message service provides queues for message consumers, and allows
a
> > > message producers to send messages to specified queues (point-to-point
> > > messaging), or to publish messages with specified topics that may be
of
> > > interest to registered consumers (publish/subscribe messaging).
> > >
> > > Messages that are sent or published to a queue are stored in memory
> > > (transient messages) or in a database (persistent messages) until they
can
> > > be delivered to the queue's consumer, which is either a client or a
> > > component. The message service provides a pull-style mechanism for
client
> > > notification, and a push-style mechanism for component notification.
> > >
> > > Once configuration is complete, the message service can be accessed by
CORBA
> > > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface,
or by
> > > Java/EJB clients using the Java Message Service (JMS) API.
> > >
> > > Hope this helps.
> > > Scott
> > >
> > > "Basant Gupta" <basantg@yahoo.com> wrote in message
> > > news:38D1CCA2.A27D53CC@yahoo.com...
> > > > Hi,
> > > > I'm not sure which release of EAServer is supposed to support
the
> > > > the Java Messaging Service (JMS). I need some clarification about
this
> > > > service.
> > > >
> > > > Is this service going to be available only to Java components
in
> > > > EAServer? Or will this service be able to be accessed by any type
of
> > > > components (PB, C++, etc), much like the CosNaming Service or the
> > > > Transaction Management Service ?
> > > >
> > > > I am currently building an application (PB server components)
which
> > > > requires asynchronous messaging. The way I currently handle this is
> > > > through polling. I am wondering if my PB components could benefit
from
> > > > the JMS service once it is implemented in EAServer.
> > > >
> > > > Regards,
> > > > Basant Gupta
> > > >
> > > >
>
> --
> Himagiri Mukkamala - EA Server Engineering,
> Sybase Inc., 510.922.5477


Glenn Santa Cruz Posted on 2000-03-20 15:45:53.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 20 Mar 2000 09:45:53 -0600
From: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Organization: Daily Access Concepts
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 123
NNTP-Posting-Host: 12.6.74.30
Message-ID: <347_38D647B1.5CD506B8@dailyaccess.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D2663C.6D85029F@yahoo.com> <347_38D29089.16224B89@sybase.com> <347_fzFcShXk$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26090
Article PK: 156095

Considering all of the moving parts involved, I'm wondering if a timeout
would occur in the blocking method call; specifically, is there a
maximum allowable time for a method to complete? 5 hours? 10 hours?
14 weeks?

Glenn

"Dave Wolf [Sybase]" wrote:
>
> Please see the IDL documentation for the module EventSamples for our design
> pattern to avoid polling the server. The basic idea is that the client
> spawns a thread and that thread makes a synchornous method call recieve().
> When the message is delivered receive() will return and the thread will call
> to its parent.
>
> This is NOT polling and handles many common issues with async event deliery
> in distributed models.
>
> Dave Wolf
> Internet Applications Division
>
> "Himagiri Mukkamala" <himagiri@sybase.com> wrote in message
> news:38D29089.16224B89@sybase.com...
> > 1) It doenst have to poll, the api has a timeout and if set
> > to low value, then it would be the equivalent of polling.
> > If not the recieve call on a queue for a message would be a
> > blocking call, so ur not polling.
> > U dont have to pass object reference, u have to pass the
> > name of the component which has a method named onMessage in
> > it.
> >
> > 2) Yes
> >
> > 3) Servlets could act like anyother java clients
> >
> > himagiri
> >
> > Basant Gupta wrote:
> > >
> > > Hi Scott,
> > > Thanks for your clarification. JMS certainlylooks promising. Could
> you
> > > provide a little more insight into the following questions.
> > >
> > > 1) From your message, "The message service provides a pull-style
> mechanism for
> > > client notification, and a push-style mechanism for component
> notification.".
> > > Does this mean that the client has to do some sort of polling. As for
> the
> > > component, does this mean that we can pass component objects by
> reference ?
> > > 2) "Once configuration is complete, the message service can be accessed
> by CORBA
> > > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface.".
> Would
> > > PowerBuilder be considered a CORBA 2.0+ client with IIOP1.0 or IIOP1.1 ?
> > > 3) This is really far-fetched but is there anyway in which HTML clients
> could
> > > benefit from this messaging service through components in EAServer
> invoked by
> > > PowerDynamo or through servelets ?
> > >
> > > Regards,
> > > Basant Gupta
> > >
> > > "Scott McReynolds [Sybase]" wrote:
> > >
> > > > Basant,
> > > >
> > > > This will be avalible with 3.6 at the latest. It may be avalible as
> an EBF,
> > > > but we are still looking into that option at this point. Here is a
> > > > description of the message service:
> > > >
> > > > The message service provides queues for message consumers, and allows
> a
> > > > message producers to send messages to specified queues (point-to-point
> > > > messaging), or to publish messages with specified topics that may be
> of
> > > > interest to registered consumers (publish/subscribe messaging).
> > > >
> > > > Messages that are sent or published to a queue are stored in memory
> > > > (transient messages) or in a database (persistent messages) until they
> can
> > > > be delivered to the queue's consumer, which is either a client or a
> > > > component. The message service provides a pull-style mechanism for
> client
> > > > notification, and a push-style mechanism for component notification.
> > > >
> > > > Once configuration is complete, the message service can be accessed by
> CORBA
> > > > 2.0+ clients with IIOP 1.0 or IIOP 1.1 using this CORBA IDL interface,
> or by
> > > > Java/EJB clients using the Java Message Service (JMS) API.
> > > >
> > > > Hope this helps.
> > > > Scott
> > > >
> > > > "Basant Gupta" <basantg@yahoo.com> wrote in message
> > > > news:38D1CCA2.A27D53CC@yahoo.com...
> > > > > Hi,
> > > > > I'm not sure which release of EAServer is supposed to support
> the
> > > > > the Java Messaging Service (JMS). I need some clarification about
> this
> > > > > service.
> > > > >
> > > > > Is this service going to be available only to Java components
> in
> > > > > EAServer? Or will this service be able to be accessed by any type
> of
> > > > > components (PB, C++, etc), much like the CosNaming Service or the
> > > > > Transaction Management Service ?
> > > > >
> > > > > I am currently building an application (PB server components)
> which
> > > > > requires asynchronous messaging. The way I currently handle this is
> > > > > through polling. I am wondering if my PB components could benefit
> from
> > > > > the JMS service once it is implemented in EAServer.
> > > > >
> > > > > Regards,
> > > > > Basant Gupta
> > > > >
> > > > >
> >
> > --
> > Himagiri Mukkamala - EA Server Engineering,
> > Sybase Inc., 510.922.5477


Evan Ireland Posted on 2000-03-20 21:29:23.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 21 Mar 2000 09:29:23 +1200
From: Evan Ireland <eireland@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Glenn Santa Cruz <spam?no.glenn_santacruz@dailyaccess.com>
Subject: Re: Java Messaging Service
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 20
NNTP-Posting-Host: vpn-eme-048.sybase.com 130.214.8.48
Message-ID: <347_38D69833.1A70FC5C@sybase.com>
References: <347_38D1CCA2.A27D53CC@yahoo.com> <347_xwHjPhCk$GA.261@forums.sybase.com> <347_38D2663C.6D85029F@yahoo.com> <347_38D29089.16224B89@sybase.com> <347_fzFcShXk$GA.111@forums.sybase.com> <347_38D647B1.5CD506B8@dailyaccess.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26055
Article PK: 156060


Glenn Santa Cruz wrote:
>
> Considering all of the moving parts involved, I'm wondering if a timeout
> would occur in the blocking method call; specifically, is there a
> maximum allowable time for a method to complete? 5 hours? 10 hours?
> 14 weeks?

There is no maximum time, however we recommend using the "default timeout"
which can be configured by the Jaguar administrator so that the message
service can detect disconnected clients. When the client receives no
messages, it just loops and tries again.
________________________________________________________________________________

Evan Ireland Sybase EAServer Engineering eireland@sybase.com
Wellington, New Zealand +64 4 934-5856