binary payloads in messages

[Ilya Grigorik]

Hey guys, quick question: will beanstalk work fine with binary
payloads? The messages we're sending in for one of our applications
are rather large, so we want to gzip the JSON before throwing it into
beanstalk. Having said that, seeing some weird behavior (getting
RESERVED but no body), etc.

ig

[Martin Sarsale]

We're gzipping the body without any problem.
Just make sure you change the max size of the job when you launch beanstalkd.

>
> ig
> >
>



--
Martin Sarsale
msn: mar...@malditainternet.com
jabber: martin....@gtalk.com
twitter: http://twitter.com/runixo
linkedin: http://www.linkedin.com/in/msarsale
sumavisos: http://www.sumavisos.com
blog: http://runa.tumblr.com

[igrigorik]

Hmm, ok, interesting. We did up the size of the body already, so this
must be something else causing the errors.

cheers,
ig

On Nov 9, 1:09 pm, Martin Sarsale <martin.sars...@gmail.com> wrote:

> On Mon, Nov 9, 2009 at 3:04 PM, Ilya Grigorik <i...@aiderss.com> wrote:
>
> > Hey guys, quick question: will beanstalk work fine with binary
> > payloads? The messages we're sending in for one of our applications
> > are rather large, so we want to gzip the JSON before throwing it into
> > beanstalk. Having said that, seeing some weird behavior (getting
> > RESERVED but no body), etc.
>
> We're gzipping the body without any problem.
> Just make sure you change the max size of the job when you launch beanstalkd.
>
>
>
> > ig
>
> --
> Martin Sarsale
> msn: mar...@malditainternet.com

> jabber: martin.sars...@gtalk.com

[Keith Rarick]

On Tue, Nov 10, 2009 at 5:25 AM, igrigorik <igri...@gmail.com> wrote:
> Hmm, ok, interesting. We did up the size of the body already, so this
> must be something else causing the errors.

Getting RESERVED with no body should simply not happen. Let me know if
you can find a way to reproduce it.

kr