Thanks George,
I will have a look.
Regards
Jim.
- Original Message -
From: "George Jagodzinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 11:22 PM
Subject: RE: OT Problem Domain question
> Flash Communication server handles
I have not heard of Jabber but I will have a look.
Regards
Jim.
- Original Message -
From: "Benjamin Tomasini" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 11:13 PM
Subject: Re: OT Problem Domain question
> Have you looked into Ja
eorge
-Original Message-
From: Jim Collins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2003 4:55 PM
To: [EMAIL PROTECTED]
Subject: Re: OT Problem Domain question
Hi Ian,
Thanks for the feedback. Sending emails to clients does not seem a
particularly elegant solution :). At the momen
m will look at something
> else (probably RMI based).
>
> Regards
>
> Jim.
> - Original Message -
> From: "Benjamin Tomasini" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 18, 2003 10:24 PM
> Subject: Re: OT Prob
ssage -
From: "Benjamin Tomasini" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 10:24 PM
Subject: Re: OT Problem Domain question
> Then you will have to embed a server in your clients. I would just poll
> the web service at regular intervals.
erations
> > [EMAIL PROTECTED]
> > (614) 213-6100
> >
> >
> >
> >
> > "Jim Collins" <[EMAIL PROTECTED]> on 06/18/2003 03:26:08 PM
> >
> > Please respond to [EMAIL PROTECTED]
> >
> > To: <[EMAIL PROTECTED]>
> > cc
Subject: Re: OT Problem Domain question
>
> Why not just include a version number with the XML feed? Your clients
will
> know it has changed if the version number increments. If you can't change
> the XML schema itself, then the version number could go in a SOAP header,
&g
ED]>
Sent: Wednesday, June 18, 2003 9:27 PM
Subject: Re: OT Problem Domain question
>
>
> Seems like a web service would be overkill for this sort of thing.
>
> What I would do is provide a server-side process that generates and
> distributes the e-mail (perl works quite n
t;Jim Poulsen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 9:32 PM
Subject: RE: OT Problem Domain question
> The most efficient way, if you have access to a MOM, is to hook them all
up
> to a topic in JMS
>
> -Original Message-
Jim Poulsen wrote:
good suggestion. you could even dynamically keep the schema up to date and
publish it for your clients at a well known URL. Or include a dynamic URL
reference to it in the SOAP message.
I wish I had thought of the simple idea of including a version number.
That may be the
:30 PM
To: [EMAIL PROTECTED]
Subject: Re: OT Problem Domain question
Why not just include a version number with the XML feed? Your clients will
know it has changed if the version number increments. If you can't change
the XML schema itself, then the version number could go in a SOAP heade
cc:
Subject: Re: OT Problem Domain question
06/19/2003
The most efficient way, if you have access to a MOM, is to hook them all up
to a topic in JMS
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2003 3:27 PM
To: [EMAIL PROTECTED]
Subject: Re: OT Problem Domain question
Jim Collins wrote:
>I hav
Jim Collins wrote:
I have a number of clients that receive an XML datafeed. This datafeed can
change due to various circumstances and I would like all the clients to be
notified of any change. Would it be possible for a Web Service to notify all
clients of a change or would the clients need to con
Enterprise Midrange - Bank One Infrastructure & Operations
[EMAIL PROTECTED]
(614) 213-6100
"Jim Collins" <[EMAIL PROTECTED]> on 06/18/2003 03:26:08 PM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: OT Problem Domain question
Hi,
I was
Hi,
I was wondering if Web Services would be applicable for the following
problem.
I have a number of clients that receive an XML datafeed. This datafeed can
change due to various circumstances and I would like all the clients to be
notified of any change. Would it be possible for a Web Service t
16 matches
Mail list logo