ALOE http://aloe-project.de/AloeFeeds/action/atomFeedResourceActivities?resourceId=mbio5F2 aloe-noreply@dfki.uni-kl.de Martin http://aloe-project.de/AloeView/action/userData?userId=lzwX6p3 This feed contains recent activities on resource "Cross-Origin Resource Sharing" in [ALOE] http://aloe-project.de/AloeFeeds/action/atomFeedResourceActivities?resourceId=mbio5F2 ALOE http://aloe-project.de/AloeFeeds/action/atomFeedResourceActivities?resourceId=mbio5F2 aloe-noreply@dfki.uni-kl.de Martin http://aloe-project.de/AloeView/action/userData?userId=lzwX6p3 http://aloe-project.de/AloeFeeds/action/atomFeedResourceActivities?resourceId=mbio5F2:6:2009-12-04 20:19:19.0 December 4, 2009 8:19:00 PM CET: User <a href="http://aloe-project.de/AloeView/action/userData?userId=lzwX6p3"><b>Martin</b></a> contributed resource <a href="http://aloe-project.de/AloeView/action/resourceDetailed?resourceId=mbio5F2"><b>Cross-Origin Resource Sharing</b></a> with the following metadata:<br/><br/><i>creator</i>: <b>W3C</b><br/><i>description</i>: <b>This document defines a mechanism to enable client-side cross-origin requests. Specifications that want to enable cross-origin requests in an API they define can use the algorithms defined by this specification. If such an API is used on http://example.org resources, a resource on http://hello-world.example can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: http://example.org as response header), which would allow that resource to be fetched cross-origin from http://example.org. </b><br/><i>license</i>: <b></b><br/><i>tags</i>: <b>resourcesharing sharing w3c</b><br/><i>title</i>: <b>Cross-Origin Resource Sharing</b><br/>