Another idea would be to use HTTP to invoke your service and rely on HTTP
caching. ODE doesn't support it completely yet but if you're willing to
help, we could give you some pointers.
Matthieu
On Wed, Jul 23, 2008 at 2:10 PM, Alex Boisvert <
boisvert@...> wrote:
> I would suggest placing a mediation service (that does caching/memoisation)
> in front of the service so that it's transparent to the process.
>
> Looks like Synapse may be able to help you with this but that's just a
> guess,
>
http://synapse.apache.org/Synapse_Configuration_Language.html#cache>
> alex
>
>
> On Wed, Jul 23, 2008 at 12:55 PM, Strub, Richard F. (GSFC-610.2)[ADNET] <
>
richard.f.strub@...> wrote:
>
> > (Sorry but I am not real clear on terms)
> >
> > I can run my 11 step process using ode.
> > I was wondering if you could give me a rough idea on how I could
> implement
> > service level caching.
> > What I would like to do is to skip a step/service/operation if the input
> is
> > the same as a previous invocation of the service.
> > Perhaps the 11 step process produces an image and the user just once to
> > re-render the image slightly.
> > Only the last, image rendering, service would need to be run.
> >
> > Somehow I store all the input, output, and results of the services in a
> > database and...?
> >
> > Thankyou.
> >
> >
>
