The following response times were measured
by browser clients connecting via
fast mobile networks with powerful smart phones:
(1) <-- start point
https://my.opalstack.com/signin/
(2)
Sign In <-- pressed
(3) <-- over 30 sec from (2)
https://my.opalstack.com/ <-- to this URL
(4) * site can't be reached * / or over 20 sec from (3)
https://my.opalstack.com/users/ <-- to this URL
(5) <-- Please, wait <-- over 10 sec from (4)
https://my.opalstack.com/applications/ <-- to this URL
(6) <-- 5-7 sec from (5)
https://my.opalstack.com/domains/ <-- to this URL
(7) <-- 5-8 sec from (6)
https://my.opalstack.com/routes/ <-- to this URL
(8) <-- 5-8 sec from (7)
https://my.opalstack.com/certificates/ <-- to this URL
(9) <--:8-9 sec from (8)
https://my.opalstack.com/mailusers/ <-- to this URL
(10) <--8-9 sec from (9)
https://my.opalstack.com/mail/ <-- to this URL
(11) <-- 2-3 sec from (10)
https://my.opalstack.com/tokens/ <-- to this URL
(12) <-- 5-8 sec from (11)
https://my.opalstack.com/usage/ <-- to this URL
Questions:
(Q1) could opalstack upgrade server to go directly
to URLs (4) ... (12) given by browser client ?
i.e.
(a) not to (3)
- but instead
(b) the same way as WebFaction server did
- because
(c) it takes too much time for server
to get all user content available to client
- and in any case because
(d) clients need only a subset content at a time
- not forgetting clients using html instructions
with URLs pointing to (4) ... (12)
(Q2) or is this feature already in your work
list and if so what is the schedule ?