Title: Message Title
|
|
Hi [~helix84], the html display was added at one point, and they currently are mostly useless. Instead of fixing them to make them more useful, I would be in favor of removing output serialization to HTML, its unnecessary, you would otherwise get json or xml, depending on your browsers preferred accept header. If you want to make HTML from the API, it would be better to use a client application, where you can put in your own business logic. One issue with just adding stylesheets is that we'll eventually support authN/authZ in the API, which means the client will need to send secrets in the call, which the stylesheets aren't going to help with.
|
|
|
|
|
REST API currently responds to requests for text/html, application/xml and application/json. The text/html output: * is very simple, does not correspond to any formal HTML standard * is not created systematically, only by concatenating strings * doesn't contain all the information returned by the other types, therefore it's nearly useless * is the onl...
|
|
|
|
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel