|
Home > Archive > Microsoft Content Management Server > February 2004 > Handling CMS Events from a Web Service
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Handling CMS Events from a Web Service
|
|
| earwicker [ch] 2004-02-09, 1:37 am |
| all---
I've got a custom HTTP module which snags CMS events with no problem
when those events are raised by the editing application that contains
the HTTP module. But what I'm wondering is this:
Is there a way to trap events raised within one CmsApplicationContext
from a DIFFERENT CmsApplicationContext?
The reason I'm asking is that I have a Web Service which provides CMS
content to a number of non-CMS sources. This Web Service knows nothing
about CMS Workflows, it only searches for and retrieves content. It
also caches what it retrieves so that it can skip CMS altogether
whenever possible. So . . . in order to present fresh data to callers
of the WS, the WS needs to catch events raised when any postings it
has cached are changed (saved, approved, declined, etc).
Hence, application 1 (editing app) raises the events, app 2 (the Web
Service) needs to catch them. Is this even theoretically possible? If
so, how? If not, any suggested workarounds?
---earwicker[ch]
| |
| Stefan [MSFT] 2004-02-09, 1:37 am |
| Hi,
I think the only workaround would be to let your applications write such
stuff to a common database and look here for the info instead of listening
to the events.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"earwicker [ch]" <earwicker@sbcglobal.net> wrote in message
news:8ea32483.0402090651.8fb6229@posting.google.com...
> all---
>
> I've got a custom HTTP module which snags CMS events with no problem
> when those events are raised by the editing application that contains
> the HTTP module. But what I'm wondering is this:
>
> Is there a way to trap events raised within one CmsApplicationContext
> from a DIFFERENT CmsApplicationContext?
>
> The reason I'm asking is that I have a Web Service which provides CMS
> content to a number of non-CMS sources. This Web Service knows nothing
> about CMS Workflows, it only searches for and retrieves content. It
> also caches what it retrieves so that it can skip CMS altogether
> whenever possible. So . . . in order to present fresh data to callers
> of the WS, the WS needs to catch events raised when any postings it
> has cached are changed (saved, approved, declined, etc).
>
> Hence, application 1 (editing app) raises the events, app 2 (the Web
> Service) needs to catch them. Is this even theoretically possible? If
> so, how? If not, any suggested workarounds?
>
> ---earwicker[ch]
|
|
|
|
|