Received: by 10.43.117.132 with SMTP id fm4mr7129572icc.1.1333442356039;
        Tue, 03 Apr 2012 01:39:16 -0700 (PDT)
X-BeenThere: beanstalk-talk@googlegroups.com
Received: by 10.50.188.136 with SMTP id ga8ls8956868igc.0.canary; Tue, 03 Apr
 2012 01:39:15 -0700 (PDT)
Received: by 10.50.163.97 with SMTP id yh1mr6903410igb.3.1333442355434;
        Tue, 03 Apr 2012 01:39:15 -0700 (PDT)
Received: by 10.50.163.97 with SMTP id yh1mr6903409igb.3.1333442355420;
        Tue, 03 Apr 2012 01:39:15 -0700 (PDT)
Return-Path: <k...@xph.us>
Received: from mail-ob0-f177.google.com (mail-ob0-f177.google.com [209.85.214.177])
        by gmr-mx.google.com with ESMTPS id hh2si849551igc.0.2012.04.03.01.39.15
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 03 Apr 2012 01:39:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of k...@xph.us designates 209.85.214.177 as permitted sender) client-ip=209.85.214.177;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of k...@xph.us designates 209.85.214.177 as permitted sender) smtp.mail...@xph.us
Received: by obbup16 with SMTP id up16so6681615obb.8
        for <beanstalk-talk@googlegroups.com>; Tue, 03 Apr 2012 01:39:15 -0700 (PDT)
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=7dxijRVZCSKgc1r1PuwUecwe/yEdY4PX1hIpsfuE3Fo=;
        b=nOUTQ99sBwwKa/eKO4rUlIrupD4ABUA7ePEs+bZe79uNgijOVaHASxm77OuEDyo9i2
         nZbXBwWLGQQ9liMTuaxsK2xP2BDAUNeH5eoyzYI32qn6LvfQDhUSXuKDHEqOSyIw1d7g
         byIG/NUB5G9j8SObEvEzGCmF7G+lDdWU0n8Q7uaCNMx1S1igOkDynnu8tTAFtbtKoIdZ
         PToBycrq5xyJSDBwhKya+Q0s8yiLNMRQPZlsZ+nHsmUOdNlLaQ8g61LJdFz3wwWiHZ74
         MFmJ0+UzDmHHXqHyt+2wVVv5r+1S2Eoq97btKcfRicVy8GjjGCLM0blFmjU8k84dizTI
         mZkA==
MIME-Version: 1.0
Received: by 10.60.169.174 with SMTP id af14mr16728059oec.13.1333442354912;
 Tue, 03 Apr 2012 01:39:14 -0700 (PDT)
Received: by 10.182.74.129 with HTTP; Tue, 3 Apr 2012 01:39:14 -0700 (PDT)
In-Reply-To: <bca3a3a8-b32a-4493-b723-87b0c2e06...@s7g2000yqm.googlegroups.com>
References: <bca3a3a8-b32a-4493-b723-87b0c2e06...@s7g2000yqm.googlegroups.com>
Date: Tue, 3 Apr 2012 01:39:14 -0700
Message-ID: <CAD25zGC4zXdMOd8hiE7fHK38NRZ96U0Y1=bVx3uTiTvSNfw...@mail.gmail.com>
Subject: Re: Peek at complete list of jobs
From: Keith Rarick <k...@xph.us>
To: beanstalk-talk@googlegroups.com
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQltO9syL446Ra3/o0FVPO4mHMNAbdgynJoroGVbATlNRfcOIaSPA+TlOQiupxI7jNo4eqj8

If you're not concerned with performance, you can
reserve all the jobs in the tube, then release
them all again. This will give you a chance to
inspect the entire contents.

kr

On Mon, Apr 2, 2012 at 2:46 AM, Jurian Sluiman <jur...@juriansluiman.nl> wrote:
> I've seen similar requests on this ML before, but am not aware if any
> progress is made since. What I am looking for is a method to peek all
> jobs, like peek and peek-* currently do for a single job. I know it
> might have drawbacks for heavy usage queues or very fast queues, but I
> think this is up to the developer to decide. If a peek-all command is
> load dependent, developers can choose whether or not to use it
> depending on their own situation.
>
> On the ML others have showed some good use cases why it might come in
> handy, and I have something similar for myself. My jobs can succeed
> (and will be deleted) or not. If not, a job might be retried later
> (e.g. a request to a 3rd party service timed out) or buried (something
> else happened). I want to use bury because it gives a user the
> possibility to delete or kick the job. In my case it is often a human
> being who can decide if a job has to be retried or deleted anyhow.
>
> For such system an interface is required to which the user can select
> one or multiple jobs to be retried and one or multiple jobs to be
> deleted. For UX reasons I cannot let the user process the buried jobs
> one by one.
>
> --
> Jurian Sluiman
>
> --
> You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
> To post to this group, send email to beanstalk-talk@googlegroups.com.
> To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
>