incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Progress on new UI
Date Sun, 27 Dec 2009 08:37:44 GMT
Agreed. Other parts of the web-ui are more impt.

Right now, I have left the various text components with default filler
text. My next step was to place the contents in a resource file for
customers to be able to change it.

On Sun, Dec 27, 2009 at 9:23 AM, Ethan Jewett <esjewett@gmail.com> wrote:
> What are we trying to accomplish with the welcome screen? It seems
> that is the question we need to answer and will pretty much decide for
> us if we need a tag cloud, messages, or something else entirely. Once
> we decide that, we should be able to implement whatever it is.
>
> For now, the fastest solution is probably something static, which we
> can replace once the final approach is decided/designed.
>
> Ethan
>
> On Saturday, December 26, 2009, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>> But the new Twitter home page does have trending topics - probably not
>> changed in real-time though. Maybe we could have a tag cloud that
>> isn't comet-based.
>>
>>
>> On Wed, Dec 23, 2009 at 9:22 PM, Vassil Dichev <vdichev@apache.org> wrote:
>>> Just to let you know, fetching messages from the public timeline is
>>> currently not cached. It probably doesn't make much sense either
>>> because it would then flood the cache too quickly with messages which
>>> are not likely to be requested again. This would result in messages
>>> being flushed from the cache too quickly.
>>>
>>> On neither of the popular microblogging sites (Twitter and identi.ca)
>>> is the public timeline updated in real-time. This makes sense because
>>> the performance overhead is significant and the benefit fairly small.
>>> In light of the recent performance benchmarks I'm not sure it's wise
>>> to update the public timeline in real-time. Maybe some sampling would
>>> emulate real-time reasonably well?
>>>
>>> Anyway, sending 20 messages instead of 1 would might waste some
>>> bandwidth, but will not cause such a performance overhead as hitting
>>> the DB.
>>>
>>> Finally, the tag clouds you see on the main page are currently based
>>> on the friends' timeline, so it is not the same for different users.
>>> It could be generated out of the last messages of the public
>>> timeline, but then it's all again about fetching the messages.
>>>
>>> Not that I'm against having some real-time functionality on the front
>>> page, but I just wanted to note that this goes beyond what just the
>>> new UI involves.
>>>
>>
>

Mime
View raw message