Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are there other APIs necessary to define any other driver's API? #16

Closed
hpoit opened this issue Jul 22, 2015 · 6 comments
Closed

Are there other APIs necessary to define any other driver's API? #16

hpoit opened this issue Jul 22, 2015 · 6 comments

Comments

@hpoit
Copy link

hpoit commented Jul 22, 2015

Hi Chris and Jesse,

Thanks for the awesome work you guys put up here.

I'm a novice... Are there any other APIs beside the CRUD for whose specs I would have to build in the case of a Julia wrapper?

Thanks! Best, Kevin

@hpoit
Copy link
Author

hpoit commented Jul 22, 2015

Hey Chris and Jesse,

Does this answer the question?

These new MongoDB drivers conform to published specifications.

  1. Server Selection - Deciding which server to send database operations to in a MongoDB deployment.
  2. Server Discovery and Monitoring - All the logic required to make a MongoDB application highly available.
  3. CRUD API - The API for how we Create, Read, Update and Delete data from MongoDB.
  4. Authentication - The rules for how to authenticate to MongoDB servers.

https://www.mongodb.com/blog/post/announcing-next-generation-drivers-mongodb

So 1 and 2 are complete (thank you), 3 partially, with 4 to be done entirely? Any other besides these?

Thanks!

@ajdavis
Copy link
Contributor

ajdavis commented Jul 22, 2015

A driver that wraps the C Driver 1.2 gets 1, 2, and 4 for free. Your user
gives you a "mongodb://" URI that expresses all the options for connecting
to the server or servers, and the C driver does the rest including
authentication. You just need to implement #3 in terms of the C Driver's
mongoc_bulk_operation_t. See the mongorover code for guidance.

On Wednesday, July 22, 2015, Kevin Liu notifications@github.com wrote:

Hey Chris and Jesse,

Does this answer the question?

These new MongoDB drivers conform to published specifications.

Server Selection - Deciding which server to send database operations
to in a MongoDB deployment.
2.

Server Discovery and Monitoring - All the logic required to make a
MongoDB application highly available.
3.

CRUD API - The API for how we Create, Read, Update and Delete data
from MongoDB.
4.

Authentication - The rules for how to authenticate to MongoDB servers.

https://www.mongodb.com/blog/post/announcing-next-generation-drivers-mongodb

So 1 and 2 are complete, and 3 partially, with 4 left to do? Thanks!


Reply to this email directly or view it on GitHub
#16 (comment)
.

@hpoit
Copy link
Author

hpoit commented Jul 23, 2015

Thank you

@hpoit
Copy link
Author

hpoit commented Jul 25, 2015

Hi Jesse. So is this the only implementation I need to wrap? https://github.com/mongodb/mongo-c-driver/blob/master/src/mongoc/mongoc-bulk-operation.c Thanks so much for your help

@christopherjwang
Copy link
Collaborator

@tenthdimension
Sorry for the late reply: I don't get any notifications for this repo.
This is what the PHP (another driver that wraps the C driver) does. It was recommended to me to do the same. I wouldn't necessarily say that it is the only implementation you need to wrap, but I would bet it would cover the majority of your use cases.

@hpoit
Copy link
Author

hpoit commented Aug 14, 2015

Hi @christopherjwang! Thanks for the advice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants