You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2009/07/15 12:59:46 UTC

Resend Functionality

Hi,

I'm not quite sure I understand the resend functionality. Tried it on
Stax and I'm not sure if it works correctly.

Like the idea that a mesage now includes a reason for appearing in
your timeline but what are the other possible reasons: "followed",
???.

It would probably be better if in the final UI, this reason was
represent by a special icon.

D.

Re: Resend Functionality

Posted by Anne Kathrine Petterøe <yo...@gmail.com>.

Thanks for doing this Vassil!
:-)


On 15. juli. 2009, at 14.35, Richard Hirsch wrote:

> Just tried them with FF 3.0.9 and they work fine.
>
> On Wed, Jul 15, 2009 at 2:33 PM, Vassil Dichev<vd...@apache.org>  
> wrote:
>>> You may want to look at the new graphs on the Stax Console (you  
>>> still
>>> have access :->), you will see exactly what memory usage in this
>>> enviroment looks like.
>>
>> I've been checking the console the last couple of weeks, I haven't
>> forgotten about the access :)
>>
>> Trying to access the graphs took a veeery long time and then they
>> appeared empty, so I decided there's something wrong with Stax  
>> itself.
>>

Re: Resend Functionality

Posted by Richard Hirsch <hi...@gmail.com>.

Just tried them with FF 3.0.9 and they work fine.

On Wed, Jul 15, 2009 at 2:33 PM, Vassil Dichev<vd...@apache.org> wrote:
>> You may want to look at the new graphs on the Stax Console (you still
>> have access :->), you will see exactly what memory usage in this
>> enviroment looks like.
>
> I've been checking the console the last couple of weeks, I haven't
> forgotten about the access :)
>
> Trying to access the graphs took a veeery long time and then they
> appeared empty, so I decided there's something wrong with Stax itself.
>

Re: Resend Functionality

Posted by Vassil Dichev <vd...@apache.org>.

> You may want to look at the new graphs on the Stax Console (you still
> have access :->), you will see exactly what memory usage in this
> enviroment looks like.

I've been checking the console the last couple of weeks, I haven't
forgotten about the access :)

Trying to access the graphs took a veeery long time and then they
appeared empty, so I decided there's something wrong with Stax itself.

Re: Resend Functionality

Posted by Richard Hirsch <hi...@gmail.com>.

You may want to look at the new graphs on the Stax Console (you still
have access :->), you will see exactly what memory usage in this
enviroment looks like.

D.

On Wed, Jul 15, 2009 at 2:08 PM, Vassil Dichev<vd...@apache.org> wrote:
> Hey, I thought you did Monday deployments only on Monday, you caught
> me by surprise in the middle of a development cycle :)
>
>> I am wondering if Vassil is the only who can see the retsent messages?
>> At least he could see my resent messages although they never showed up in my
>> timeline.
>
> A message will not appear in your timeline if it's already there. The
> whole point of resending messages was that the message is not
> duplicated like it is with the numerous retweets in Twitter. This
> means that the resender will not see a change in her/his timeline,
> which is a bit unfortunate, because we don't have any feedback that
> something has happened. Perhaps an icon could change or the button
> could disappear, or a status message could appear... Please bear with
> me, I'll eventually get it right.
>
>> Actually right now none of my messages show up in the timeline. I just sent
>> 4 and they all disappeared.
>
> There seem to be some stability issues, which we also experienced the
> last weeks independently of the newly developed features. Maybe this
> is memory-related, but it's hard to confirm. Not sure how much memory
> we need, but I remember reading somewhere that Stax limits memory to
> 256MB, which might be a bit too tight for a servlet container,
> embedded database (!) and 2 actor implementations running at the same
> time.
>
>
>> I'm not quite sure I understand the resend functionality. Tried it on
>> Stax and I'm not sure if it works correctly.
>
> Actually I've just made explicit what was already in ESME. Even before
> the changes, there was the "resend" action, but it would run only if
> the message satisfies the filter criteria. The only thing that's
> changed now is that you can invoke this action manually for a message,
> and you can also see the reason of the message (which was stored in
> the timeline data in the DB, but just wasn't displayed). Try a
> "resend" action on esme.us or esmecloudserver.dickhirsch.staxapps.net
> to see what I mean (e.g. filter "any" will catch all messages).
>
>> Like the idea that a mesage now includes a reason for appearing in
>> your timeline but what are the other possible reasons: "followed",
>
> The reason is information about how the message got to your timeline.
> It's especially useful in the context of resent messages, because all
> of a sudden you'll see messages in your timeline from users, which
> you're not even following. The reason is not a part of the message
> itself and can be different for the same message but for different
> users. Each of the hooks has a different reason, but we might not
> display that information, because it's duplicated a lot with the
> message source.
>
>> It would probably be better if in the final UI, this reason was
>> represent by a special icon.
>
> Absolutely, I didn't want to focus on this right now. I think there
> are too many columns right now and it's better to represent some of
> this information with visual cues- (color? icons?).
>
>
> Vassil
>

Re: Resend Functionality

Posted by Vassil Dichev <vd...@apache.org>.

Hey, I thought you did Monday deployments only on Monday, you caught
me by surprise in the middle of a development cycle :)

> I am wondering if Vassil is the only who can see the retsent messages?
> At least he could see my resent messages although they never showed up in my
> timeline.

A message will not appear in your timeline if it's already there. The
whole point of resending messages was that the message is not
duplicated like it is with the numerous retweets in Twitter. This
means that the resender will not see a change in her/his timeline,
which is a bit unfortunate, because we don't have any feedback that
something has happened. Perhaps an icon could change or the button
could disappear, or a status message could appear... Please bear with
me, I'll eventually get it right.

> Actually right now none of my messages show up in the timeline. I just sent
> 4 and they all disappeared.

There seem to be some stability issues, which we also experienced the
last weeks independently of the newly developed features. Maybe this
is memory-related, but it's hard to confirm. Not sure how much memory
we need, but I remember reading somewhere that Stax limits memory to
256MB, which might be a bit too tight for a servlet container,
embedded database (!) and 2 actor implementations running at the same
time.


> I'm not quite sure I understand the resend functionality. Tried it on
> Stax and I'm not sure if it works correctly.

Actually I've just made explicit what was already in ESME. Even before
the changes, there was the "resend" action, but it would run only if
the message satisfies the filter criteria. The only thing that's
changed now is that you can invoke this action manually for a message,
and you can also see the reason of the message (which was stored in
the timeline data in the DB, but just wasn't displayed). Try a
"resend" action on esme.us or esmecloudserver.dickhirsch.staxapps.net
to see what I mean (e.g. filter "any" will catch all messages).

> Like the idea that a mesage now includes a reason for appearing in
> your timeline but what are the other possible reasons: "followed",

The reason is information about how the message got to your timeline.
It's especially useful in the context of resent messages, because all
of a sudden you'll see messages in your timeline from users, which
you're not even following. The reason is not a part of the message
itself and can be different for the same message but for different
users. Each of the hooks has a different reason, but we might not
display that information, because it's duplicated a lot with the
message source.

> It would probably be better if in the final UI, this reason was
> represent by a special icon.

Absolutely, I didn't want to focus on this right now. I think there
are too many columns right now and it's better to represent some of
this information with visual cues- (color? icons?).


Vassil

Re: Resend Functionality

Posted by Richard Hirsch <hi...@gmail.com>.

On Wed, Jul 15, 2009 at 2:13 PM, Vassil Dichev<vd...@apache.org> wrote:
> Thanks, I'll look into it. It doesn't look related to the new code.
>
> At first glance, it seems strange- the code can't find a message by
> id, and it already got the id from another finder method... Probably
> some of the finder overriding that I did a while ago in relation to
> pools. Maybe somebody tried to resend a message from a pool, which the
> others had no rights to view...

I think that was exactly what I tried to do. Would have to test again
to check it.

D.

Re: Resend Functionality

Posted by Vassil Dichev <vd...@apache.org>.

Thanks, I'll look into it. It doesn't look related to the new code.

At first glance, it seems strange- the code can't find a message by
id, and it already got the id from another finder method... Probably
some of the finder overriding that I did a while ago in relation to
pools. Maybe somebody tried to resend a message from a pool, which the
others had no rights to view...


On Wed, Jul 15, 2009 at 2:27 PM, Richard Hirsch<hi...@gmail.com> wrote:
> Looks like there is some sort of an exception:
>
> ava.util.NoSuchElementException: None.get
>        at scala.None$.get(Option.scala:150)
>        at scala.None$.get(Option.scala:148)
>        at org.apache.esme.comet.Timeline$$anonfun$2.apply(Timeline.scala:62)
>        at org.apache.esme.comet.Timeline$$anonfun$2.apply(Timeline.scala:62)
>        at scala.List.map(List.scala:812)
>        at org.apache.esme.comet.Timeline.render(Timeline.scala:62)
>        at net.liftweb.http.CometActor$class.net$liftweb$http$CometActor$$performReRender(CometActor.scala:485)
>        at net.liftweb.http.CometActor$$anonfun$net$liftweb$http$CometActor$$_mediumPriority$1.apply(CometActor.scala:380)
>        at net.liftweb.http.CometActor$$anonfun$net$liftweb$http$CometActor$$_mediumPriority$1.apply(CometActor.scala:343)
>        at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:38)
>        at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
>        at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11$$anonfun$apply$12.apply(CometActor.scala:308)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11$$anonfun$apply$12.apply(CometActor.scala:307)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$.functionLifespan(S.scala:1105)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11.apply(CometActor.scala:307)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11.apply(CometActor.scala:307)
>        at net.liftweb.http.S$.net$liftweb$http$S$$wrapQuery(S.scala:909)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1$$anonfun$apply$18.apply(S.scala:1027)
>        at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:846)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$doAround$1.apply(S.scala:847)
>        at net.liftweb.mapper.MetaProtoExtendedSession$myWrapper$.apply(ProtoExtendedSession.scala:71)
>        at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:847)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1.apply(S.scala:1025)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$.net$liftweb$http$S$$_nest2InnerInit(S.scala:1024)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24$$anonfun$apply$25$$anonfun$apply$26.apply(S.scala:1045)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24$$anonfun$apply$25.apply(S.scala:1044)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24.apply(S.scala:1043)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23.apply(S.scala:1042)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22.apply(S.scala:1041)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21.apply(S.scala:1040)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1.apply(S.scala:1039)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$.net$liftweb$http$S$$_innerInit(S.scala:1038)
>        at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30$$anonfun$apply$31$$anonfun$apply$32.apply(S.scala:1069)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30$$anonfun$apply$31.apply(S.scala:1068)
>        at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5$$anonfun$apply$6.apply(Vars.scala:197)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5.apply(Vars.scala:196)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4.apply(Vars.scala:195)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.RequestVarHandler$$anonfun$apply$3.apply(Vars.scala:194)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.RequestVarHandler$.apply(Vars.scala:193)
>        at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30.apply(S.scala:1067)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29.apply(S.scala:1066)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$$anonfun$_init$1.apply(S.scala:1065)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.S$._init(S.scala:1064)
>        at net.liftweb.http.S$.init(S.scala:780)
>        at net.liftweb.http.S$.initIfUninitted(S.scala:1347)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10.apply(CometActor.scala:306)
>        at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10.apply(CometActor.scala:306)
>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>        at net.liftweb.http.CometActor$$anon$1.apply(CometActor.scala:305)
>        at net.liftweb.http.CometActor$$anon$1.apply(CometActor.scala:303)
>        at scala.actors.Reaction.run(Reaction.scala:78)
>        at scala.actors.FJTask$Wrap.run(Unknown Source)
>        at scala.actors.FJTaskRunner.scanWhileIdling(Unknown Source)
>        at scala.actors.FJTaskRunner.run(Unknown Source)
>
>
> On Wed, Jul 15, 2009 at 1:21 PM, Anne Kathrine
> Petterøe<yo...@gmail.com> wrote:
>> I am wondering if Vassil is the only who can see the retsent messages?
>> At least he could see my resent messages although they never showed up in my
>> timeline.
>>
>> Actually right now none of my messages show up in the timeline. I just sent
>> 4 and they all disappeared.
>>
>> And it shouldn't be a problem to exchange the reasons with icons in the new
>> UI.
>> But we will still focus on getting a working UI up and running first, the
>> "plastic surgery" will have to wait for now.
>>
>> /Anne
>>
>> On 15. juli. 2009, at 12.59, Richard Hirsch wrote:
>>
>>> Hi,
>>>
>>> I'm not quite sure I understand the resend functionality. Tried it on
>>> Stax and I'm not sure if it works correctly.
>>>
>>> Like the idea that a mesage now includes a reason for appearing in
>>> your timeline but what are the other possible reasons: "followed",
>>> ???.
>>>
>>> It would probably be better if in the final UI, this reason was
>>> represent by a special icon.
>>>
>>> D.
>>
>>
>

Re: Resend Functionality

Posted by Richard Hirsch <hi...@gmail.com>.

Looks like there is some sort of an exception:

ava.util.NoSuchElementException: None.get
	at scala.None$.get(Option.scala:150)
	at scala.None$.get(Option.scala:148)
	at org.apache.esme.comet.Timeline$$anonfun$2.apply(Timeline.scala:62)
	at org.apache.esme.comet.Timeline$$anonfun$2.apply(Timeline.scala:62)
	at scala.List.map(List.scala:812)
	at org.apache.esme.comet.Timeline.render(Timeline.scala:62)
	at net.liftweb.http.CometActor$class.net$liftweb$http$CometActor$$performReRender(CometActor.scala:485)
	at net.liftweb.http.CometActor$$anonfun$net$liftweb$http$CometActor$$_mediumPriority$1.apply(CometActor.scala:380)
	at net.liftweb.http.CometActor$$anonfun$net$liftweb$http$CometActor$$_mediumPriority$1.apply(CometActor.scala:343)
	at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:38)
	at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
	at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11$$anonfun$apply$12.apply(CometActor.scala:308)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11$$anonfun$apply$12.apply(CometActor.scala:307)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$.functionLifespan(S.scala:1105)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11.apply(CometActor.scala:307)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10$$anonfun$apply$11.apply(CometActor.scala:307)
	at net.liftweb.http.S$.net$liftweb$http$S$$wrapQuery(S.scala:909)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1$$anonfun$apply$18.apply(S.scala:1027)
	at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:846)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$doAround$1.apply(S.scala:847)
	at net.liftweb.mapper.MetaProtoExtendedSession$myWrapper$.apply(ProtoExtendedSession.scala:71)
	at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:847)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1.apply(S.scala:1025)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$.net$liftweb$http$S$$_nest2InnerInit(S.scala:1024)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24$$anonfun$apply$25$$anonfun$apply$26.apply(S.scala:1045)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24$$anonfun$apply$25.apply(S.scala:1044)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply$24.apply(S.scala:1043)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23.apply(S.scala:1042)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21$$anonfun$apply$22.apply(S.scala:1041)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$$anonfun$apply$21.apply(S.scala:1040)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1.apply(S.scala:1039)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$.net$liftweb$http$S$$_innerInit(S.scala:1038)
	at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30$$anonfun$apply$31$$anonfun$apply$32.apply(S.scala:1069)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30$$anonfun$apply$31.apply(S.scala:1068)
	at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5$$anonfun$apply$6.apply(Vars.scala:197)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5.apply(Vars.scala:196)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4.apply(Vars.scala:195)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.RequestVarHandler$$anonfun$apply$3.apply(Vars.scala:194)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.RequestVarHandler$.apply(Vars.scala:193)
	at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29$$anonfun$apply$30.apply(S.scala:1067)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$29.apply(S.scala:1066)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$$anonfun$_init$1.apply(S.scala:1065)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.S$._init(S.scala:1064)
	at net.liftweb.http.S$.init(S.scala:780)
	at net.liftweb.http.S$.initIfUninitted(S.scala:1347)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10.apply(CometActor.scala:306)
	at net.liftweb.http.CometActor$$anon$1$$anonfun$apply$10.apply(CometActor.scala:306)
	at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
	at net.liftweb.http.CometActor$$anon$1.apply(CometActor.scala:305)
	at net.liftweb.http.CometActor$$anon$1.apply(CometActor.scala:303)
	at scala.actors.Reaction.run(Reaction.scala:78)
	at scala.actors.FJTask$Wrap.run(Unknown Source)
	at scala.actors.FJTaskRunner.scanWhileIdling(Unknown Source)
	at scala.actors.FJTaskRunner.run(Unknown Source)


On Wed, Jul 15, 2009 at 1:21 PM, Anne Kathrine
Petterøe<yo...@gmail.com> wrote:
> I am wondering if Vassil is the only who can see the retsent messages?
> At least he could see my resent messages although they never showed up in my
> timeline.
>
> Actually right now none of my messages show up in the timeline. I just sent
> 4 and they all disappeared.
>
> And it shouldn't be a problem to exchange the reasons with icons in the new
> UI.
> But we will still focus on getting a working UI up and running first, the
> "plastic surgery" will have to wait for now.
>
> /Anne
>
> On 15. juli. 2009, at 12.59, Richard Hirsch wrote:
>
>> Hi,
>>
>> I'm not quite sure I understand the resend functionality. Tried it on
>> Stax and I'm not sure if it works correctly.
>>
>> Like the idea that a mesage now includes a reason for appearing in
>> your timeline but what are the other possible reasons: "followed",
>> ???.
>>
>> It would probably be better if in the final UI, this reason was
>> represent by a special icon.
>>
>> D.
>
>

Re: Resend Functionality

Posted by Anne Kathrine Petterøe <yo...@gmail.com>.

I am wondering if Vassil is the only who can see the retsent messages?
At least he could see my resent messages although they never showed up  
in my timeline.

Actually right now none of my messages show up in the timeline. I just  
sent 4 and they all disappeared.

And it shouldn't be a problem to exchange the reasons with icons in  
the new UI.
But we will still focus on getting a working UI up and running first,  
the "plastic surgery" will have to wait for now.

/Anne

On 15. juli. 2009, at 12.59, Richard Hirsch wrote:

> Hi,
>
> I'm not quite sure I understand the resend functionality. Tried it on
> Stax and I'm not sure if it works correctly.
>
> Like the idea that a mesage now includes a reason for appearing in
> your timeline but what are the other possible reasons: "followed",
> ???.
>
> It would probably be better if in the final UI, this reason was
> represent by a special icon.
>
> D.