Subject: Re: [xsl] LINQ to XML versus XSLT From: "James A. Robinson" <jim.robinson@xxxxxxxxxxxx> Date: Fri, 27 Jun 2008 12:35:36 -0700 |
> >>>>> "James" == James A Robinson <jim.robinson@xxxxxxxxxxxx> writes: > > James> could get at or talk to via XSLT. Once you've got a way of > James> running HTTP POST operations from XSLT, > > That's xsl:result-document. Heh, well there's a problem trying to do that. If you've got a service where you POST a request and expect to read a reponse document, then xsl:result-document isn't so hot. We are in fact playing around with using xsl:result-document and using URI #fragments to indicate write vs read, but I'm not sold that it's the best way to handle things. We've also got some custom extensions for http:* operations, but we're still exploring the best way to handle these things. Jim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - James A. Robinson jim.robinson@xxxxxxxxxxxx Stanford University HighWire Press http://highwire.stanford.edu/ +1 650 7237294 (Work) +1 650 7259335 (Fax)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] LINQ to XML versus XSLT, Colin Paul Adams | Thread | RE: [xsl] LINQ to XML versus XSLT, Houghton,Andrew |
Re: [xsl] LINQ to XML versus XSLT, James A. Robinson | Date | Re: [xsl] LINQ to XML versus XSLT, Colin Paul Adams |
Month |