Hi, Nelson,
From within the MarkLogic organization we too would like to hear about
implementations! I think that for any CRUD and search applications, the
REST API will meet most needs out of the box.
We know about the need for a join operation, and I've got as a TODO to
write a custom constraint that will implement a join as you've described
it. I'll make sure the list hears about it when I've done so.
Enforcing node value uniqueness is a new idea for the REST API. My own
inclination (since I'm far from XQuery phobic) would be to implement a
pre-commit trigger for this; the trigger wouldn't interfere with other
aspects of REST API operation. In general we're working out what code
really needs to live close to the server and what kinds of operations
can be shipped off to a REST client.
Hope that helps a little, and bring on your further experiences please,
Charles
On 12/14/2012 12:29 PM, Nelson Wells wrote:
Hi all,
We're exploring options for interacting with MarkLogic without writing XQuery
code. We currently do CRUD operations in MarkLogic with our own custom REST
endpoints, and this particular flavor proven a little too hands on. We're
looking at another, more generic REST interface developed by another team
in the organization, and also the new REST interface introduced in ML6.
I haven't gotten a chance to get my hands dirty with the new API, but I've read
the developer's guide and the API docs and I'm liking what I'm seeing.
In the time between now and my own experiments, can anyone give an example of
when the REST API did not meet your needs, or under what circumstances you've
needed to extend the interface? Off the top of my head, it seems like an
extension would have to be written when a join is required and you don't want
to have to make two HTTP requests and aggregate them in the consuming
application. Also, I haven't read anything about maintaining node value
uniqueness across an entire database other than searching first before doing an
insert or update, but this may not be specific to the new REST API.
Any insight would be appreciated.
Thanks,
Nelson
NOTICE OF CONFIDENTIALITY: This electronic message, including attachments, is
for the sole use of the named recipient and may contain confidential or
privileged information protected by State of Tennessee and Federal regulations.
Any unauthorized review, use, disclosure, copying or distribution is strictly
prohibited. If you are not the intended recipient or have received this
communication in error please contact the sender or email
[email protected] and destroy all copies of the original message. Thank
you.
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
--
Charles Greer
Senior Engineer
MarkLogic Corporation
[email protected]
Phone: +1 707 408 3277
www.marklogic.com
This e-mail and any accompanying attachments are confidential. The information
is intended solely for the use of the individual to whom it is addressed. Any
review, disclosure, copying, distribution, or use of this e-mail communication
by others is strictly prohibited. If you are not the intended recipient, please
notify us immediately by returning this message to the sender and delete all
copies. Thank you for your cooperation.
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
