Hello Shawn,
Thanks a lot for your answer. It did help me a lot.
Regards,
Damian
On 7/20/2016 2:21 PM, Shawn McKinney wrote:
On Jul 20, 2016, at 4:08 AM, Damianos Metallidis <[email protected]> wrote:
want to ask a more technical question being adapted for the project of
directory-fortress-commander. Let's say that i want to calculate the execution
time of the user's page (this can be done with various monitoring tools) , can
you please tell me which are the processes/methods that we could consider as
backend so as to measure the execution of users pages?
For example i see that it creates 4 panels so maybe the creation of each of the
panels is the execution time we need?
What's your opinion about that(of course based on fortress :)
Yes there are four panels - list, detail, navigation and info. Of those 4, the
first two, list and detail, are the only ones that matter, from a execution
time measurement perspective.
As to how to measure - depends on the operation being performed. The list
panel is for searches, the detail is (mostly) for add, update, delete, although
it does perform searches, for loading the various dropdowns and modals that are
in play.
If I were you, I’d start simple. The list panel is probably where you start.
Every time you load the page, or hit the search button there is a roundtrip
with the server, where the data gets pulled back (from LDAP) and the pages are
rendered. Those are the most costly operations in this component.
From there, when you click on an item in the list box, an ajax call is made,
where that record is ‘sent’ to the detail panel for display and edit purposes.
Each time you click, another roundtrip to load the info into the detail panel.
From there you can do other operations, either add, update, delete or search
dependent on which button you click in the detail panel. Everything routes
through the wicket application, which has an MVC, component based web
architecture.
