Hi Thilina, Definitely the client should listen. Thinking of an example; The OUT MEP is like a news feed and Axis Engine is like the CNN who will send out messages in the event of say.. some breaking news. CNN already know whom to send, meaning there should be some means of subscription which is not relevant to our MEP. But when the event is fired the messages will be sent out and the Clients better be ready to accept it.
Think the confusion comes because of the assumption of HTTP transport which is two way. It will make perfect sense if you think of a Transports like SMTP. Regards Chathura > -----Original Message----- > From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 17, 2005 12:25 PM > To: [email protected]; Ajith Ranabahu > Subject: Re: [Axis2] Out Message (Auto start web service) > > > > > > > Note : I just class form Thread to show the ability of > > > wring a service which send out messages ( but latter it has to be > implements > > > a well defined interface instated of extending from Thread.) > > > > > > ( This kind of web service is useful in to subscribers > > > etc. ) > > for WS- eventing :). > > I just need to get clarified how the client will capture these message. > do the client has to have listeners wating for mesages. I'm asking > this generally about web services. This is something bothered me for > some time. > > regards, > Thilina
