Sleepy.Mongoose: A MongoDB HTTP Interface

Posted bykchodorowPosted inMongoDB, too-popularTags:, ,

The first half of the MongoDB book is due this week, so I wrote a REST interface for Mongo (I’m a prolific procrastinator).  Anyway, it’s called Sleepy.Mongoose and it’s available at https://github.com/10gen-labs/sleepy.mongoose.

Installing Sleepy.Mongoose

  1. Install MongoDB.
  2. Install the Python driver: 
    $ easy_install pymongo
  3. Download Sleepy.Mongoose.
  4. From the mongoose directory, run: 
    $ python httpd.py

You’ll see something that looks like:

=================================
|      MongoDB REST Server      |
=================================

listening for connections on http://localhost:27080

Using Sleepy.Mongoose

First, we’re just going to ping Sleepy.Mongoose to make sure it’s awake. You can use curl:

$ curl 'http://localhost:27080/_hello'

and it’ll send back a Star Wars quote.

To really use the interface, we need to connect to a database server. To do this, we post our database server address to the URI “/_connect” (all actions start with an underscore):

$ curl --data server=localhost:27017 'http://localhost:27080/_connect'

This connects to the database running at localhost:27017.

Now let’s insert something into a collection.

$ curl --data 'docs=[{"x":1}]' 'http://localhost:27080/foo/bar/_insert'

This will insert the document {“x” : 1} into the foo database’s bar collection. If we open up the JavaScript shell (mongo), we can see the document we just added:

> use foo
> db.bar.find()
{ "_id" : ObjectId("4b7edc9a1d41c8137e000000"), "x" : 1 }

But why bother opening the shell when we can query with curl?

$ curl -X GET 'http://localhost:27080/foo/bar/_find'
{"ok": 1, "results": [{"x": 1, "_id": {"$oid": "4b7edc9a1d41c8137e000000"}}], "id": 0}

Note that queries are GET requests, whereas the other requests up to this point have been posts (well, the _hello can be either).

A query returns three fields:

  • “ok”, which will be 1 if the query succeeded, 0 otherwise
  • “results” which is an array of documents from the db
  • “id” which is an identifier for that particular query

In this case “id” is irrelevant as we only have one document in the collection but if we had a bunch, we could use the id to get more results (_find only returns the first 15 matching documents by default, although it’s configurable). This will probably be clearer with an example, so let’s add some more documents to see how this works:

$ curl --data 'docs=[{"x":2},{"x":3}]' 'http://localhost:27080/foo/bar/_insert'
{"ok" : 1}

Now we have three documents. Let’s do a query and ask for it to return one result at a time:

$ curl -X GET 'http://localhost:27080/foo/bar/_find?batch_size=1'
{"ok": 1, "results": [{"x": 1, "_id": {"$oid": "4b7edc9a1d41c8137e000000"}}], "id": 1}

The only difference between this query and the one above is the “?batch_size=1” which means “send one document back.” Notice that the cursor id is 1 now, too (not 0). To get the next result, we can do:

$ curl -X GET 'http://localhost:27080/foo/bar/_more?id=1&batch_size=1'
{"ok": 1, "results": [{"x": 2, "_id": {"$oid": "4b7ee0731d41c8137e000001"}}], "id": 1}
$ curl -X GET 'http://localhost:27080/foo/bar/_more?id=1&batch_size=1'
{"ok": 1, "results": [{"x": 3, "_id": {"$oid": "4b7ee0731d41c8137e000002"}}], "id": 1}

Now let’s remove a document:

$ curl --data 'criteria={"x":2}' 'http://localhost:27080/foo/bar/_remove'
{"ok" : 1}

Now if we do a _find, it only returns two documents:

$ curl -X GET 'http://localhost:27080/foo/bar/_find'
{"ok": 1, "results": [{"x": 1, "_id": {"$oid": "4b7edc9a1d41c8137e000000"}}, {"x": 3, "_id": {"$oid": "4b7ee0731d41c8137e000002"}}], "id": 2}

And finally, updates:

$ curl --data 'criteria={"x":1}&newobj={"$inc":{"x":1}}' 'http://localhost:27080/foo/bar/_update'

Let’s do a _find to see the updated object, this time using criteria: {“x”:2}. To put this in a URL, we need to escape the ‘{‘ and ‘}’ characters. You can do this by copy-pasting it into any javascript interpreter (Rhino, Spidermonkey, mongo, Firebug, Chome’s dev tools) as follows:

> escape('{"x":2}')
%7B%22x%22%3A2%7D

And now we can use that in our URL:

$ curl -X GET 'http://localhost:27080/foo/bar/_find?criteria=%7B%22x%22%3A2%7D'
{"ok": 1, "results": [{"x": 2, "_id": {"$oid": "4b7edc9a1d41c8137e000000"}}], "id": 0}

If you’re looking to go beyond the basic CRUD, there’s more documentation in the wiki.

This code is super-alpha. Comments, questions, suggestions, patches, and forks are all welcome.

Note: Sleepy.Mongoose is an offshoot of something I’m actually supposed to be working on: a JavaScript API we’re going to use to make an awesome sharding tool.  Administrating your cluster will be a point-and-click interface.  You’ll be able to see how everything is doing, drag n’ drop chunks, visually split collections… it’s going to be so cool.

186 thoughts on “Sleepy.Mongoose: A MongoDB HTTP Interface”

  1. Do you think this will end up being the preferred method of exposing MongoDB data via REST? There is currently “experimental” REST support built in to the server itself and from a performance standpoint that seems like it could be a better solution.

    Like

    Reply

  2. Do you think this will end up being the preferred method of exposing MongoDB data via REST? There is currently “experimental” REST support built in to the server itself and from a performance standpoint that seems like it could be a better solution.

    Like

    Reply

  3. > Do you think this will end up being the preferred method of exposing
    > MongoDB data via REST?

    Unless some 3rd party has a better one that they’re going to release, yes. If people actually use sleepy.monoose, it’ll become a top-level “driver” and have its own jira section, move to github.com/mongodb, etc.

    The “REST support” built into the database is and always will be pretty lean. We (MongoDB devs) don’t want to compromise overall performance by making the database do too much.

    Agreed that it probably isn’t the fastest thing ever, but if you’re using REST, you’re probably not too concerned with speed anyway. It is built on top of the Python driver for a variety of reasons: Python comes with a web server, it should encourage more user contributions than if it was written in something super-speedy like C, and my boss told me to. If people really need more speed eventually, it could easily be rebuilt in C.

    Like

    Reply

  4. > Do you think this will end up being the preferred method of exposing
    > MongoDB data via REST?

    Unless some 3rd party has a better one that they’re going to release, yes. If people actually use sleepy.monoose, it’ll become a top-level “driver” and have its own jira section, move to github.com/mongodb, etc.

    The “REST support” built into the database is and always will be pretty lean. We (MongoDB devs) don’t want to compromise overall performance by making the database do too much.

    Agreed that it probably isn’t the fastest thing ever, but if you’re using REST, you’re probably not too concerned with speed anyway. It is built on top of the Python driver for a variety of reasons: Python comes with a web server, it should encourage more user contributions than if it was written in something super-speedy like C, and my boss told me to. If people really need more speed eventually, it could easily be rebuilt in C.

    Like

    Reply

  5. I am looking at writing a php interface that only exposes the database over localhost and contains a few functions for user authentication that use PHP sessions. This would be used by AJAX applications. My question is about how I should handle the more advanced queries and aggregations. Currently I would have the javascript pass a JSON object in a POST request to the PHP handler.

    Like

    Reply

  6. I am looking at writing a php interface that only exposes the database over localhost and contains a few functions for user authentication that use PHP sessions. This would be used by AJAX applications. My question is about how I should handle the more advanced queries and aggregations. Currently I would have the javascript pass a JSON object in a POST request to the PHP handler.

    Like

    Reply

  9. I have been successful in the first 3 steps of installations, but I get the following error (step-4):

    # python httpd.py
    Traceback (most recent call last):
    File “httpd.py”, line 16, in ?
    from handlers import MongoHandler
    File “/home/mahmoud/downloads/kchodorow-sleepy.mongoose-9440233/handlers.py”, line 23, in ?
    import simplejson as json
    ImportError: No module named simplejson

    any help is appreciated.

    To verify that I have pymongo, I did:

    # python
    Python 2.4.3 (#1, Jan 21 2009, 01:11:33)
    [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
    Type “help”, “copyright”, “credits” or “license” for more information.
    >>> import pymongo
    >>> connection = pymongo.Connection(“localhost”, 27017)
    Thu Apr 15 15:22:20 connection accepted from 127.0.0.1:47319 #1
    >>> Thu Apr 15 15:22:20 end connection 127.0.0.1:47319
    db = connection.test
    >>> db.name()
    pymongo/helpers.py:140: DeprecationWarning: ‘Database.name()’ has been deprecated and will be removed. Please use ‘Database.name’ instead.
    DeprecationWarning)
    u’test’

    Like

    Reply

  10. I have been successful in the first 3 steps of installations, but I get the following error (step-4):

    # python httpd.py
    Traceback (most recent call last):
    File “httpd.py”, line 16, in ?
    from handlers import MongoHandler
    File “/home/mahmoud/downloads/kchodorow-sleepy.mongoose-9440233/handlers.py”, line 23, in ?
    import simplejson as json
    ImportError: No module named simplejson

    any help is appreciated.

    To verify that I have pymongo, I did:

    # python
    Python 2.4.3 (#1, Jan 21 2009, 01:11:33)
    [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
    Type “help”, “copyright”, “credits” or “license” for more information.
    >>> import pymongo
    >>> connection = pymongo.Connection(“localhost”, 27017)
    Thu Apr 15 15:22:20 connection accepted from 127.0.0.1:47319 #1
    >>> Thu Apr 15 15:22:20 end connection 127.0.0.1:47319
    db = connection.test
    >>> db.name()
    pymongo/helpers.py:140: DeprecationWarning: ‘Database.name()’ has been deprecated and will be removed. Please use ‘Database.name’ instead.
    DeprecationWarning)
    u’test’

    Like

    Reply

  13. Hello Kristina,

    Sorry for bugging you, I get the following error (using centos 64 bits).
    Many thanks in advance.

    # easy_install json
    Searching for json
    Reading http://pypi.python.org/simple/json/
    Couldn’t find index page for ‘json’ (maybe misspelled?)
    Scanning index of all packages (this may take a while)
    Reading http://pypi.python.org/simple/
    No local packages or download links found for json
    Best match: None
    Traceback (most recent call last):
    File “/usr/bin/easy_install”, line 7, in ?
    sys.exit(
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1712, in main
    with_ei_usage(lambda:
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1700, in with_ei_usage
    return f()
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1716, in
    distclass=DistributionWithoutHelpCommands, **kw
    File “/usr/lib64/python2.4/distutils/core.py”, line 149, in setup
    dist.run_commands()
    File “/usr/lib64/python2.4/distutils/dist.py”, line 946, in run_commands
    self.run_command(cmd)
    File “/usr/lib64/python2.4/distutils/dist.py”, line 966, in run_command
    cmd_obj.run()
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 211, in run
    self.easy_install(spec, not self.no_deps)
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 434, in easy_install
    self.local_index
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/package_index.py”, line 475, in fetch_distribution
    return dist.clone(location=self.download(dist.location, tmpdir))
    AttributeError: ‘NoneType’ object has no attribute ‘clone’

    Like

    Reply

  14. Hello Kristina,

    Sorry for bugging you, I get the following error (using centos 64 bits).
    Many thanks in advance.

    # easy_install json
    Searching for json
    Reading http://pypi.python.org/simple/json/
    Couldn’t find index page for ‘json’ (maybe misspelled?)
    Scanning index of all packages (this may take a while)
    Reading http://pypi.python.org/simple/
    No local packages or download links found for json
    Best match: None
    Traceback (most recent call last):
    File “/usr/bin/easy_install”, line 7, in ?
    sys.exit(
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1712, in main
    with_ei_usage(lambda:
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1700, in with_ei_usage
    return f()
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 1716, in
    distclass=DistributionWithoutHelpCommands, **kw
    File “/usr/lib64/python2.4/distutils/core.py”, line 149, in setup
    dist.run_commands()
    File “/usr/lib64/python2.4/distutils/dist.py”, line 946, in run_commands
    self.run_command(cmd)
    File “/usr/lib64/python2.4/distutils/dist.py”, line 966, in run_command
    cmd_obj.run()
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 211, in run
    self.easy_install(spec, not self.no_deps)
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py”, line 434, in easy_install
    self.local_index
    File “/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/package_index.py”, line 475, in fetch_distribution
    return dist.clone(location=self.download(dist.location, tmpdir))
    AttributeError: ‘NoneType’ object has no attribute ‘clone’

    Like

    Reply

  15. OK, I installed using :

    yum install python-json

    then
    python httpd.py

    =================================
    | MongoDB REST Server |
    =================================

    listening for connections on http://localhost:27080

    it worked.

    Thank you Kristina!

    Like

    Reply

  16. OK, I installed using :

    yum install python-json

    then
    python httpd.py

    =================================
    | MongoDB REST Server |
    =================================

    listening for connections on http://localhost:27080

    it worked.

    Thank you Kristina!

    Like

    Reply

  17. Hello Kristina,

    Have you seen the following error:

    1. start sleepy.mongoose

    [mahmoud@localhost kchodorow-sleepy.mongoose-9440233]$ python httpd.py

    =================================
    | MongoDB REST Server |
    =================================

    listening for connections on http://localhost:27080

    2. issue _hello as:

    [mahmoud@localhost ~]$ curl ‘http://localhost:27080/_hello’
    curl: (52) Empty reply from server

    3. sleepy.mongoose server gives the following error:

    —————————————-
    Exception happened during processing of request from (‘127.0.0.1’, 53027)
    Traceback (most recent call last):
    File “/usr/lib64/python2.4/SocketServer.py”, line 222, in handle_request
    self.process_request(request, client_address)
    File “/usr/lib64/python2.4/SocketServer.py”, line 241, in process_request
    self.finish_request(request, client_address)
    File “/usr/lib64/python2.4/SocketServer.py”, line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
    File “/usr/lib64/python2.4/SocketServer.py”, line 521, in __init__
    self.handle()
    File “/usr/lib64/python2.4/BaseHTTPServer.py”, line 316, in handle
    self.handle_one_request()
    File “/usr/lib64/python2.4/BaseHTTPServer.py”, line 310, in handle_one_request
    method()
    File “httpd.py”, line 130, in do_GET
    (uri, args, type) = self.process_uri(“GET”)
    File “httpd.py”, line 100, in process_uri
    (uri, q, args) = self.path.partition(‘?’)
    AttributeError: ‘str’ object has no attribute ‘partition’
    —————————————-

    Like

    Reply

  18. Hello Kristina,

    Have you seen the following error:

    1. start sleepy.mongoose

    [mahmoud@localhost kchodorow-sleepy.mongoose-9440233]$ python httpd.py

    =================================
    | MongoDB REST Server |
    =================================

    listening for connections on http://localhost:27080

    2. issue _hello as:

    [mahmoud@localhost ~]$ curl ‘http://localhost:27080/_hello’
    curl: (52) Empty reply from server

    3. sleepy.mongoose server gives the following error:

    —————————————-
    Exception happened during processing of request from (‘127.0.0.1’, 53027)
    Traceback (most recent call last):
    File “/usr/lib64/python2.4/SocketServer.py”, line 222, in handle_request
    self.process_request(request, client_address)
    File “/usr/lib64/python2.4/SocketServer.py”, line 241, in process_request
    self.finish_request(request, client_address)
    File “/usr/lib64/python2.4/SocketServer.py”, line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
    File “/usr/lib64/python2.4/SocketServer.py”, line 521, in __init__
    self.handle()
    File “/usr/lib64/python2.4/BaseHTTPServer.py”, line 316, in handle
    self.handle_one_request()
    File “/usr/lib64/python2.4/BaseHTTPServer.py”, line 310, in handle_one_request
    method()
    File “httpd.py”, line 130, in do_GET
    (uri, args, type) = self.process_uri(“GET”)
    File “httpd.py”, line 100, in process_uri
    (uri, q, args) = self.path.partition(‘?’)
    AttributeError: ‘str’ object has no attribute ‘partition’
    —————————————-

    Like

    Reply

  21. Here are the versions:

    [mahmoud@localhost]$ /usr/bin/python -V
    Python 2.4.3
    [mahmoud@localhost]$ /usr/bin/python
    Python 2.4.3 (#1, Jan 21 2009, 01:11:33)
    [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
    Type “help”, “copyright”, “credits” or “license” for more information.
    >>>

    Like

    Reply

  22. Here are the versions:

    [mahmoud@localhost]$ /usr/bin/python -V
    Python 2.4.3
    [mahmoud@localhost]$ /usr/bin/python
    Python 2.4.3 (#1, Jan 21 2009, 01:11:33)
    [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
    Type “help”, “copyright”, “credits” or “license” for more information.
    >>>

    Like

    Reply

    1. Hi Kristina,

      Like many other people here, I’m stuck at JSONP usage to overcome cross-domain issue. The response header says 200 OK, however the response is empty. Is there ANY work-around to this? Greatly appreciate the help. Thank you!

      -Amol

      Like

      Reply

  25. Hi,

    first of all I really appreciate your work! I’m doing my diploma thesis at the moment and I search for alternatives to Amazon S3. MongoDB seems to be a very good choice and sleepy.mongoose seems to do a good job with the REST part. Is there a possibility to realize authentication over this? Like a signature for the Requests that will ensure integrity and identity?

    thy

    Like

    Reply

  26. Hi,

    first of all I really appreciate your work! I’m doing my diploma thesis at the moment and I search for alternatives to Amazon S3. MongoDB seems to be a very good choice and sleepy.mongoose seems to do a good job with the REST part. Is there a possibility to realize authentication over this? Like a signature for the Requests that will ensure integrity and identity?

    thy

    Like

    Reply

  27. Good idea, I’ve started adding https support. Keep your eye out for version 0.02 on Github. I’ll probably also do a follow-up blog post when I release it, so subscribe to my RSS feed! That way I can let people know about some of the features that aren’t covered in this intro post (security, multiple connections, etc.)

    Like

    Reply

  28. Good idea, I’ve started adding https support. Keep your eye out for version 0.02 on Github. I’ll probably also do a follow-up blog post when I release it, so subscribe to my RSS feed! That way I can let people know about some of the features that aren’t covered in this intro post (security, multiple connections, etc.)

    Like

    Reply

  31. Hi Kristina.

    I’m trying to connect on Mongodb with your REST interface from my Cocoa projects and I’ve got some questions:
    -How did you manage the credentials? With HTTP authentication?
    -Why does we need to connect first to the database? How can I close this connection?

    Thanks for your answer and for your work. I have subscribed to your feed 🙂

    Like

    Reply

  32. Hi Kristina.

    I’m trying to connect on Mongodb with your REST interface from my Cocoa projects and I’ve got some questions:
    -How did you manage the credentials? With HTTP authentication?
    -Why does we need to connect first to the database? How can I close this connection?

    Thanks for your answer and for your work. I have subscribed to your feed 🙂

    Like

    Reply

  33. > -How did you manage the credentials? With HTTP authentication?

    Right now, sleepy.mongoose doesn’t do https connections, you can only connect over http. I’m working on https for the next version (expect it out by June). For MongoDB authentication, you can use the authenticate db command (see the core docs for more info and the Sleepy.Mongoose docs on running database commands).

    > -Why does we need to connect first to the database? How can I close
    > this connection?

    Sleepy.Mongoose doesn’t run a MongoDB server, it just connects to them. This is kind of nice, as you can connect to multiple database servers from your application (see the Connections section of the Sleepy.Mongoose readme).

    Like

    Reply

  34. > -How did you manage the credentials? With HTTP authentication?

    Right now, sleepy.mongoose doesn’t do https connections, you can only connect over http. I’m working on https for the next version (expect it out by June). For MongoDB authentication, you can use the authenticate db command (see the core docs for more info and the Sleepy.Mongoose docs on running database commands).

    > -Why does we need to connect first to the database? How can I close
    > this connection?

    Sleepy.Mongoose doesn’t run a MongoDB server, it just connects to them. This is kind of nice, as you can connect to multiple database servers from your application (see the Connections section of the Sleepy.Mongoose readme).

    Like

    Reply
  41. Pingback: Mongo DB and the REST API | Matthew Cluver
  42. Pingback: links for 2010-08-23 | Neyric.com

  43. Hi kristina,

    at first thank you very much! You do here a great work for mongodb!

    I have problems with auth. I tried it with :
    curl –data username=myusername&pass=mypass ‘http://localhost:27080/_auth’

    But it don´t work for me. Maybe you can post an example in the wiki.

    Thanks in advance

    keep on rocking 😉

    Like

    Reply

  44. Hi, thank you for your great work!
    I was trying to connect to Sleepy.mongoose over jQuery.ajax, and had no luck to receive ‘data’ in the ‘success’ function.
    I realize that it’s cross-domain and JSONP related problem, and compared it to a Flickr example on jQuery.getJSON page. The data returned by Flickr JSONP API is something like jsonp123456({DATA}) and Sleepy.Mongoose’s is {DATA} without jsonp123456() attached.
    My question is: does sleepy.mongoose support JSONP calling via jQuery ajax related method? If yes, what’s the right way to do it?
    Thank you again.
    Will

    Like

    Reply

      1. Hi Kristina,

        Like Will above, I am also trying to access Sleepy.Mongoose using jQuery getJSON() method and have found the same cross-domain issue. Are there plans to update Sleepy.mongoose to be JSONP compliant? If not, do you have a method of using jQuery getJSON() that might get around the cross-domain issue? Thanks for your help.

        Matt

        Like

      2. To get around the cross domain issue, you can proxy sleepy.mongoose through your web server.  I use nginx.  Here is my config:

           location /database/ {
              proxy_pass      http://sleepy;
           }

          upstream sleepy {
            server 127.0.0.1:27080;
          }

        Note that nginx and sleepy are on the same server.  Then just use:

        var request = new XMLHttpRequest(); request.open(‘GET’, ‘/database/collection/_find’, true); … var data = JSON.parse(request.responseText)[‘results’];

        Like

      1. How it make using mongoose?
        $ curl -X GET ‘http://localhost:27080/foo/bar/_find?criteria=…’
        criteria={“$explain”:”true”} — not work
        $ curl -X GET ‘http://localhost:27080/foo/bar/_find?explain=true’ — not work

        Like

      2. You have to include the query you want explained. So:

        $ curl -X GET ‘http://localhost:27080/foo/bar/_find?criteria={“query”:{…},”$explain”:true}

        where {…} is replaced by your actual query (or {}) and the whole string is properly escaped.

        Like

      3. 😦
        Its work in mongo shell (db.bar.find({“query”:{},”$explain”:true});)
        and dont work in mongoose
        curl -X GET ‘http://localhost:27080/foo/bar/_find?criteria=%7B%22query%22%3AD B%7D%2C%22%24explain%22%3Atrue%7D’
        (criteria={“query”:{},”$explain”:true})
        result is empty: {“ok”: 1, “results”: [], “id”: 30}

        Like

      4. Sorry, you’re right. Python driver’s fault 😛

        I just added support for it if you download the latest code. Do:

        curl 'http://localhost:27080/foo/bar/_find?explain=true'

        Like

  46. Just to note, the quote handling for curl is a bit different on Windows:

    > curl ‘http://localhost:27080/_hello’
    curl: (1) Unsupported protocol: ‘http

    > curl http://localhost:27080/_hello
    {“ok” : 1, “msg” : “Uh, we had a slight weapons malfunction, but uh… everything’s perfectly all right now. We’re fine. We’re all fine here now, thank you. How are you?”}

    > curl –data server=localhost:27017 http://localhost:27080/_connect
    {“ok” : 1, “host” : “localhost”, “port” : 27017, “name” : “default”}

    > curl –data docs=[{“x”:1}] http://localhost:27080/foo/bar/_insert
    {“oids”: [{“$oid”: “4d0ae6b1efe8e96d90000003”}]}

    >curl -X GET http://localhost:27080/foo/bar/_find?batch_size=1
    {“ok”: 1, “results”: [{“x”: 1, “_id”: {“$oid”: “4d0ae545efe8e96d90000001”}}], “id”: 2}

    > curl -V
    curl 7.16.4 (i686-pc-mingw32) libcurl/7.16.4 zlib/1.2.3
    Protocols: tftp ftp telnet dict ldap http file
    Features: Largefile libz

    Like

    Reply

      1. thanks for the reply. Do you think this web service could be used in production for very simple applications (simple facebook app)?

        Like

      3. thanks for the reply. Do you think this web service could be used in production for very simple applications (simple facebook app)?

        Like

  48. Hi Kristina, thanks for the great help. This is my second day with MongoDB. I could successfully run the sleepymongoose via HTML/JS. Could you please tell me how to store the response in a JS variable instead of txt file with JSON object? Sorry for asking such a naive question. -sagar

    Like

    Reply

  49. Wow this is very cool. Thank you for taken the time to write this. I was wondering how I can use this with an Flash AIR application. I need my application to connect directly to a local MongoDb and also connect to a remote Master MongoDB. I will have several AIR client applications that will need to receive db updates from this master remote db but also be able to run off the local db if the connection to the master db is lost.

    I look forward to you comments.

    Joe

    Like

    Reply

  50. Wow this is very cool. Thank you for taken the time to write this. I was wondering how I can use this with an Flash AIR application. I need my application to connect directly to a local MongoDb and also connect to a remote Master MongoDB. I will have several AIR client applications that will need to receive db updates from this master remote db but also be able to run off the local db if the connection to the master db is lost.

    I look forward to you comments.

    Joe

    Like

    Reply

    1. Sleepy.Mongoose does not manage replica set connections for you, but it certainly lets you connect to multiple servers and manage them on your own.

      Like

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

%d bloggers like this: