From: | Victoria Henry <vhenry(at)pivotal(dot)io> |
---|---|
To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
Cc: | harshal(dot)dhumal(at)enterprisedb(dot)com, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: RM#3294 - User need to reset the layout to see the changed preferences parameters |
Date: | 2018-06-12 16:22:09 |
Message-ID: | CANxYE3J4wD1ZqyqTJV2Jv69_UWg7ky7bFzw=S8r4MOz_NtfOSg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Aditya,
It is not possible to fire event in another tab/new browser window. For
>>> example, query tool can be open in another tab. And thus, changes are not
>>> reflected there. There are solutions available like updating the
>>> localStorage of the browser but those are not reliable and does not work
>>> properly on different browsers.
>>>
>> To communicate between browser tabs we can use cookie polling on client
>> side it self (at least it will avoid polling over http).
>> The main tab will update only preference specific cookie when preference
>> is updated and other tabs will poll required cookies (not all)
>> with specific interval (1 second can be configurable).
>>
> Polling is a solution but I think it should be the last option. http polls
> will not be required anyway as we have preference cache in the browser
> object.
>
Maybe it's better to poll only when an editor is open in a separate
window? What would we be polling for and how would be tell the backend
that something changed during the poll?
Thanks
Victoria & Joao
From | Date | Subject | |
---|---|---|---|
Next Message | Victoria Henry | 2018-06-12 19:04:08 | Re: [pgadmin][patch] Electron version 4.X |
Previous Message | Victoria Henry | 2018-06-12 16:06:19 | Re: [pgAdmin4][Patch]: RM 3362 - Fix the functions for PG v11, and add support procedure for PG v11 |