[GitHub] [sling-org-apache-sling-servlets-get] YegorKozlov commented on pull request #11: SLING-11892: OSGi flag to enable exporting binary properties in JSON

["YegorKozlov (via GitHub)" <gi...@apache.org>]

YegorKozlov commented on PR #11:
URL: https://github.com/apache/sling-org-apache-sling-servlets-get/pull/11#issuecomment-1572163648

   @rombert @joerghoh I like the selector idea.  It makes this feature dynamic per-request. 
   
   There is a related PR https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/22 to make sense of the base64 data when importing content via Sling POST servlet, and the question is  if it's  okay to use a colon prefixed property to carry the data?
   Sling POST Servlet ignores form properties starting with ":" with respect to content update. 
   What about importing content from json? If the GET servlet produces a JSON with colon-prefixed fields, should they be ignored when importing via Sling POST servlet? Or designating binary properties with a leading colon is just a naming convention?
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org