[TAVERNA-712] Investigate the effects of Linked Data compliance in BioCatalogue

• Type: Task
• Status: To Do
• Priority: Major
• Resolution: Unresolved
• Component/s: Taverna Workbench
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 23/Jun/10 10:07
• Updated: 28/Apr/15 11:42

Description

BioCatalogue currently performs content negotiation based on the Accept HTTP header set by the API client. In this case two network accesses need to be made at each request - initial client's request is followed by a redirect to the actual resource to be used which is fetched with a second request.

If network latency is noticeable, this slows down the plugin by a factor of two.

For now, the BioCatalogueAPIClient avoid content negotiation by suffixing all request URLs with ".xml" to use the XML endpoints directly and improve performance. (This is done centrally in a single place in the code - so it is easy to "switch off" this feature.)

Need to understand whether such behaviour can be kept or something else needs to be done.