In general I agree with you, that's the simplest
OP had a dual need. which is storing information about the asset in the
JCR at the same time, which I don't see how your solution handles.
--
Jason
On Sat, Jan 28, 2017, at 02:08 PM, Henry Saginor wrote:
> In my opinion Sling is first and
Hi Jason,
Possibly I approached it from the wrong angle in my assessment, happy to
hear it's been working for you and others. I may try again for APIs in
future.
That aside, after using sling for serving web content I can't recommend it
enough. For me it certainly puts the fun back in web
I'm not sure how to correctly convey my confusion over your statement :)
There may be some bias here, since I've been doing this for a while, but
this is an incredibly easy platform for REST and I haven't ran across
another that gives me the same flexibility.
--
Jason
On Sat, Jan 28, 2017, at
Hi Roy,
Yes my reference to data/content was based on the OP stating he'll be
storing data in JCR, so effectively yes he probably could just use a JCR
repo backend.
I'm not totally discounting Sling as an API platform, just that it probably
won't integrate easily with other API frameworks (e.g.
