+1
On Fri, Sep 18, 2009 at 10:19 AM, Eran Hammer-Lahav <> wrote:
> I like this answer.
>
> It shows that with a little code, include can be accomplished by the server without having to make the client (literally) go through hoops. I made that point on the call, that I expect smart XRD hosting services to offer this as a feature.
>
> EHL
>
> -----Original Message-----
> From: [mailto:] On Behalf Of Martin Atkins
> Sent: Friday, September 18, 2009 10:06 AM
> To:
> Subject: Re: Should XRD allow including other XRD documents?
>
>
>
> My gut feeling here is that for the unusual case where you want to use
> an XRD hosted by someone else but make a small change to it you can
> expend a little extra effort and generate an XRD that contains the
> information from the target XRD, either dynamically or statically as a
> one-off. (If you do the latter, it is of course your responsibility to
> update it when the target changes.)
>
> In other words, right now including other XRDs seems to me to be enough
> of a corner-case that the burden should be put on the XRD host, not on
> the client.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
--
--Breno
+1 (650) 214-1007 desk
+1 (408) 212-0135 (Grand Central)
MTV-41-3 : 383-A
PST (GMT-8) / PDT(GMT-7)
