Hi, Two suggestions to make addDatastream for inline content more flexible:
* Instead of uploading the content first and then giving a reference in dsLocation (2 web service calls with additional (temporary?) storage) it would be nice to supply the content directly, maybe in place of the dsLocation (1 web service call and no need for additional storage). * I'm not quite sure why the restriction that inline content must be XML. This seems to have several drawbacks: Not every content is natively XML, The XML currently gets parsed on the server side and then re-serialized which is a seemingly unnecessary performance overhead, the previous item seems to also break checksums in some cases. Wouldn't it be much easier to just accept any input, XML encode non-XML characters on the server and just write it into the FoXML? Cheers, Carsten
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
