{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/37f16626f8d6312ccfa0036065e1884c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"37f16626f8d6312ccfa0036065e1884c","url":"https://api.github.com/users/si14","login":"si14","id":316910},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-13T19:43:39Z","comments":0,"closed_at":null,"url":"https://api.github.com/repos/davisp/jiffy/issues/9","body":"Just a thought: maybe it would be a good idea to put some constraints on the input size (which should be overridable, of course)? The reason is that a long-running NIF will ruin an Erlang VM's scheduler, so it's not too wise to throw too much JSON in a single call. We can prevent this mistake by uploading an encoding/decoding to a separate thread or by putting constraints. I think the latter is easier. ","html_url":"https://github.com/davisp/jiffy/issues/9","number":9,"title":"Some sort of size limitation","id":2222789,"created_at":"2011-11-13T19:43:39Z"},"action":"opened"}