Will do. I should be able to come back to you in 1-2 days.
Thanks
Seb
Sent from my iPhone
> On 1/09/2016, at 8:18 PM, Maxim Solodovnik wrote:
>
> Hello Sebastian,
>
> I believe user list should work better after my today's commits
> Could you please check?
>
>> On Wed, Aug 24, 2016 at 10:35
Hello Sebastian,
I believe user list should work better after my today's commits
Could you please check?
On Wed, Aug 24, 2016 at 10:35 AM, Maxim Solodovnik
wrote:
> BTW Sebastien has modified jquery-ui dialog buttons, so now each has a
> name, you might wand to try to write some UI tests (using
BTW Sebastien has modified jquery-ui dialog buttons, so now each has a
name, you might wand to try to write some UI tests (using wicket tester or
selenium :)) )
On Wed, Aug 24, 2016 at 10:22 AM, Maxim Solodovnik
wrote:
> Some actions can be done on the client only (without roundtrips to the
> se
Some actions can be done on the client only (without roundtrips to the
server :) not much of them, but it can easily be done :))
On Sun, Aug 21, 2016 at 2:14 PM, seba.wag...@gmail.com <
seba.wag...@gmail.com> wrote:
> Yeah same here. Even more confusing when I look at it and kind of remember
> ho
Yeah same here. Even more confusing when I look at it and kind of remember
how it is basically mirroring some of the code and structure that initially
was in the OpenLaszlo client :D
But overall I think it's pretty cool how less code you can write the UI
with. My only concern with Wicket is that y
by design client is being created in websocket.onConnect method and being
destroyed in websocket.onDisconnect (something like this)
I'll try to double check all this on all steps
Then can fix, and/or describe :)
I wrote this lng time ago, need to refresh my memories :)
On Sun, Aug 21, 2016 at
Hi Maxim,
yeah I understand, I think those steps:
1) change right for the particular user
2) send rightUpdated event
3) each user will update their list with the data from server Hashmap
When you say (3) "each user will update their list" => You mean the visible
user list right? Cause that part
All clients are being stored in huge hashMap on the server
the idea was
1) change right for the particular user
2) send rightUpdated event
3) each user will update their list with the data from server Hashmap
I'll double check this next week
On Sun, Aug 21, 2016 at 10:57 AM, seba.wag...@gmail.com
I understand that you want to get a stable version out. So performance is
second priority. But you agree to the maths? It's quite obvious to me that
you will run into issues with large number of users with that approach.
Especially since the re-rendering of the user list happens on every right
chan
Thanks for the pointer,
but so fat I see no performance degradation
I'll optimize things as soon as any issues will arise
currently flash room is unable to hold more than 10 people (according to
one of the user report)
On Sun, Aug 21, 2016 at 8:35 AM, seba.wag...@gmail.com <
seba.wag...@gmail.com
Hi Maxim,
I have seen an example where we store the firstname/lastname in the
database instead of the session of the "Client".
RoomClientPanel.java::43
User u = getBean(UserDao.class).get(c.getUserId());
Just please keep in mind that access the database is always expensive. It's
not really suit
11 matches
Mail list logo
