I'm definitely in favor of using pipes.  It seems like a better solution.
 I've not done much with pipes (besides using them at the command line) so
I don't usually reach for them.

On Thu, Jun 27, 2013 at 3:58 PM, dlecocq <notifications@github.com> wrote:

> In lib/qless/worker.rb:
>
> >        rescue SystemCallError
> >          nil
> >        end
> >      end
> >
> > +    def write_error_to_file(e)
> > +      File.write("#{Process.pid}", Marshal.dump(e))
>
> FWIW, this <http://ruby-doc.org/core-1.8.7/IO.html#method-c-pipe> is the
> piping I'm talking about. If folks are on board, I'm happy to make the
> change. It just seems like if we're forking then that's the easy way to
> exchange information and we don't have to mess with the filesystem or redis
> keys.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/seomoz/qless/pull/121/files#r4929047>
> .
>