shinypb / openkeyval Goto Github PK

Hi,

there seems to be a limitation of 512 characters for setting a value (via JSONP).

I am making a request to http://api.openkeyval.org/store/?somekey=somevalue&jsonp_callback=...

When strlen(somevalue)==512, it works fine, but when strlen(somevalue)>=513, the new value isn't stored. I still get status 200 back, the keys-array however is empty.

Have a look over at php.net, looks like some specific patch of PHP defaults to only allow 512 characters in $_GET-variables: http://www.php.net/manual/en/reserved.variables.get.php#101469

Sincerely, Christoffer

When you create a key with any number of spaces as the value, the key is deleted.

For example, space=%20& , gets deleted. However, space=%20a%20 , works as expected.

When setting the value for a key, the same read-only key is always returned. The value of that key is always the original value. Any subsequent changes to the value with the read/write-key do not change the value of the read-only key.

Hi!

I've written a wrapper for the openkeyval API:

https://github.com/rogeriopvl/node-openkeyval

It's available through npm (npm install openkeyval).

It's still in the early stages, but fully supports get and posts in http and https.

Cheers.

This would allow you to have something like a lock file that multiple clients could share.

Without knowing if the key already existed when writing, someone else could have written to the lock file in the time between you last checking if it existed, and writing to it.

Would this be useful?

Something like:

{
   "status":"multiset",
   "keys":[
      {
         "key":"testing1",
         "read_only_key":"rok-459f1694e2455461b1186749aaf3f949eba8a134",
         "new":"true"
      },
      {
         "key":"testing2",
         "read_only_key":"rok-ee9efec3c53f048a34dba2b923ddbdaa8693aead",
         "new":"false"
      }
   ],
   "documentation_url":"http:\/\/openkeyval.org\/"
}

Some characters are being escaped which are consistent with php magic quotes being on.

$ cat test.txt 
' " \
abc123!@#$%^&*()_+=-`~;:/?><,.{}[]|

$ curl -F "data=<test.txt;type=text/plain" http://api.openkeyval.org/hello
{"status":"set","key":"hello","read_only_key":"rok-088ec226a37329f3980db9ab5082c

$ curl http://api.openkeyval.org/hello
\' \" \\
abc123!@#$%^&*()_+=-`~;:/?><,.{}[]|

the documentation states that keys are limited to 128 characters but in fact http://api.openkeyval.org/store/ is refusing keys greater than 64 chars.

curl -d "data=%00" api.openkeyval.org/testing
{"error":"missing_field","message":"Data must be sent as form data in the field 'data'","documentation_url":"http://openkeyval.org/"}

If you removed PHP from the picture and used Nginx to pass requests directly to membase (membase is like memcached but it saves to disk) then you would see a large increase in performance. PHP just isn't needed unless you work out some auth/API key scheme and have to check requests.

Even then, you can by-pass PHP for the GET requests and just use it for the SET requests.

Please add a favicon to openkeyval. It's messing up my nameless bookmarks.

JSONP is nice but simple XHR could work if
headers['Access-Control-Allow-Origin'] = '*'
is added on the server.

Querying a data store is not returning JSON. It's just a string of text.

hi guys,

today I've hacked something both awesome and wrong. long story short, this commit:
tomash/flyingv@77e3a11
lets one store files in OKV, with auto splitting of large files (and auto merging on retrieval) to save them into separate keys.

this can be used to put large amounts of data on OKV. at the moment the only limit is that "master" value that stores a JSON array of keys of all the file chunks (although the file can be rebuilt without that, as every chunk value stores the key of "next" chunk) -- this array of keys cannot be larger than 64kB, but even assuming 100 bytes for "file chunk" key it gives 640 chunks which means 40 meg of file size limit.

I don't want to pull this code off github and don't want OKV to go down because of exploitation -- maybe you can impose some limits? (POST requests per hour or something?)

Seems that openkeyval.org has stopped allowing me to commit data since the beginning of the year.

The following example works

curl -d "data=California" http://api.openkeyval.org/location

The following doesn't

curl -d "data=California" http://api.openkeyval.org/location-345345345

Trying to store data to a key that does not exist yet, gives the following error.

{"error":"save_failed","documentation_url":"http:\/\/openkeyval.org\/" 

Should be a constant, and maybe default to /var/tmp/openkeyval instead.

Dean Edward's packer has a lower compression ratio than minification+gzip, and there's a performance overhead when unpacking a packed script.

It is very easy to serve gzipped script on S3/Cloudfront: minify the script using Google's Closure Compiler, gzip the script, remove the .gz extension, upload to S3 and add "Content-Encoding: gzip" as a cutom header.

Edit: Oops, misunderstood how HTTPS works. This isn't necessary.

A write-once key is a key that can only be written to once, after that it becomes read only.

I'm trying to put together a kind of message board application, and I would like to stop people from editing their posts after posting.

$ curl -d "data=3" api.openkeyval.org/testing

$ curl api.openkeyval.org/testing

3

$ curl -d "data=0" api.openkeyval.org/testing

$ curl api.openkeyval.org/testing

{"error":"not_found","documentation_url":"http://openkeyval.org/"}

Hi, I've installed openkeyval on a server, but I can't store data.

This error returns when I try to save data with curl:

Fatal error: Call to a member function get() on a non-object in /home/myuser/mykeyvalserver/server.inc on line 106

Thanks for creating openkeyval.

yes, I know it's not the code issue, but still -- openkeyval.org is down

1. Create a namespace for counters, such as /counter-*
2. Getting the value will increment an integer, starting at 1
3. Counters cannot be written to
4. Get operation is atomic

Keys that I know are valid and are using the full 128 byte keyspace(thus the probability of a collision is very low) are gone the next day.

400 Bad Request
[('date', 'Fri, 05 Nov 2010 18:39:20 GMT'), ('connection', 'close'), ('x-powered-by', 'PHP/5.2.6-1+lenny9'), ('content-type', ''), ('server', 'Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny9 with Suhosin-Patch')]


Not sure if this is entirely necessary, but perhaps to check if a key exists without downloading it?