There is full-feature REST API in 2015.3FT which is useable for our purposes. We need to get rid of older custom REST classes and start to use builtin 2015.3.
This implies migration to the different paradigm - we have client-side projections, not directly accessible to the server (like it was in prior implementation).
There is full-feature REST API in 2015.3FT which is useable for our purposes. We need to get rid of older custom REST classes and start to use builtin 2015.3.
This implies migration to the different paradigm - we have client-side projections, not directly accessible to the server (like it was in prior implementation).