On Thu, 2006-04-20 at 10:26 +0100, Paul Fremantle wrote: > Glen > > I'm also +1. Should we think of it as mediating a generic XML/HTTP > get?
We already handle this with the Axis2 REST support. I don't think we should dilute from the stmt that messages flowing thru Synapse are SOAP messages. If they're XML/HTTP (or foo/HTTP) then they show up with the way we handle them in Axis2. > Or as a specific extension to Synapse just for WSDL and Policy? I've been thinking about this and it seems to me there are two levels of mediation Synapse can offer: a low level model where there are messages flowing thru and u mess with them as they flow thru and a higher level model where Synapse virtually hosts services which it mediates forward. That means in those cases Synapse handles ?wsdl, ?policy etc. properly. (That's basically the WS gateway model). I think we can have both in one but my current instinct is that the configs have to be kept separate. That could change as we explore this more. Asankha, Saminda and I have been playing with some ideas for the config model. We'll send that out tomorrow. Sorry about today's chat Glen - let's chat next week about it after reviewing it via the mailing list (along with Paul's proposal). Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
