Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates
 209.85.213.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Jg2euX1i1wNBgbZh2wPsMBSasRFYlbv1LhPXgUmersnsYpuc5wvleyPpLKz0RyRVDi
         WgT8L3d6oL6eGdzxjXoE+l1wmgX77aHp16SUhlr5ySZo9n3iUnQGHp9l9Gxb0ArU3s4d
         dkDn/8OfDiqFmwNHR3/IXNGXafXkS/RApAelc=
MIME-Version: 1.0
In-Reply-To: <3DDA16A54B8D40DAAE642AE443D664F9@imtiaz20100131>
References: <AANLkTikMUP78t1EfYdzeJTQ3RWrmXdW=nGcScVNYiCLq@mail.gmail.com>
	<AANLkTi=HPn4VU0+jym5KebVS+2c45iYfN9ze++J5v6AB@mail.gmail.com>
	<3DDA16A54B8D40DAAE642AE443D664F9@imtiaz20100131>
Date: Tue, 31 Aug 2010 08:07:24 +0200
Message-ID: <AANLkTi=jGqfx2=7ZafkXtqf3ii1Nyh1vTis6_MXdVrag@mail.gmail.com>
Subject: Re: New issues - a couple of blockers for 1.1 release
From: Ethan Jewett <esjewett@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

The issue doesn't happen with Popular Messages, only with Popular Links.

I need to look into the implementation, but I have a feeling the
Popular Links issue is going to be a headache. I believe that for a
given link there is no way to tell what message it shows up in, which
would make it impossible to tell if it is a link from a pooled message
or not. We may have to modify the data model for storing links to flag
the ones that started out in a pooled message...

Regarding Pubsubhubbub, as Dick said, there's no hurry. I don't think
I'll be working on it over the next couple of weeks.

Thanks for all your efforts!

Ethan

On Tue, Aug 31, 2010 at 4:20 AM, Imtiaz Ahmed H E <in.imtiaz@gmail.com> wro=
te:
> Re https://issues.apache.org/jira/browse/ESME-267
>
> I haven't tried this but plan to fix it right away.
>
> Tell me, is it only the links showing up in 'Popular Links' or is that a
> problem with the message itself also showing up in 'PopularMessages'
>
> Looks like I'll never get going with pubsubhubub ! First there was Dick's
> Release Planning mail with the pending 1.1 issues and now here are some
> more. Plan to get going after all 1.1 ending issues are resolved.
>
> However, Ethan it was your issue originally and if you feel you want to t=
ake
> it back again to push it to closure faster or something please do, otherw=
ise
> I'll re-start on it once 1.1 is done...
>
> Imtiaz
>
> ----- Original Message ----- From: "Richard Hirsch" <hirsch.dick@gmail.co=
m>
> To: <esme-dev@incubator.apache.org>
> Sent: Monday, August 30, 2010 12:00 AM
> Subject: Re: New issues - a couple of blockers for 1.1 release
>
>
>> On Sun, Aug 29, 2010 at 7:59 PM, Ethan Jewett <esjewett@gmail.com> wrote=
:
>>>
>>> Hi all,
>>>
>>> I've created a few new issues in the Jira based on my testing of the
>>> latest Stax deployment as well as some local testing. I see a couple
>>> of them as blockers of the 1.1 release (ESME-266 is definitely
>>> debatable, but I'm pretty adamant about ESME-267 as it's a real
>>> security issue):
>>>
>>> ESME-266 - https://issues.apache.org/jira/browse/ESME-266 - Some
>>> RSS/Atom feeds don't work properly. Normally I would have pushed this
>>> to the backlog, but it makes it so that we can't import Twitter feeds,
>>> which I think is pretty important.
>>
>> +1
>>
>>>
>>> ESME-267 - https://issues.apache.org/jira/browse/ESME-267 - "Links
>>> from messages in pools show up in "Popular links" for users that are
>>> not in the pool" - I put an example into the ticket of why this is a
>>> big problem
>>
>> +1 =A0- have you tried to see if resending messages in pools has the sam=
e
>> problem?
>>
>>>
>>> ESME-268 - https://issues.apache.org/jira/browse/ESME-268 - User
>>> should not be offered the option to "resend" his/her own messages.
>>> This is assigned to release 1.2 as I don't believe it is a major
>>> issue. If it is fixed before Dick tags release 1.1, then I'm in favor
>>> of including it.
>>
>> I agree as well
>>
>>
>> Thanks for checking for bugs. I'm sure after we create a RC and people
>> start testing we will probably find more bugs.
>>>
>>> Ethan
>>>
>
>