topic Re: Why does Share use javascript callbacks? in Alfresco Archive

Why does Share use javascript callbacks?

matjazmuhic — Tue, 27 Mar 2012 12:16:45 GMT

It was one of the questions in Alfresco certification exam and I have no idea why.I thought that it decreases the loading time of a web page.Is this correct?

Re: Why does Share use javascript callbacks?

mikeh — Tue, 27 Mar 2012 13:16:06 GMT

Do you remember the exact question? Seems a little odd…

Thanks,
Mike

Re: Why does Share use javascript callbacks?

matjazmuhic — Wed, 28 Mar 2012 07:51:56 GMT

I don't remember the exact question. But I think it was almost exactly like:"Why does Alfresco Share use callbacks?". Something very similar to that.

I remember the possible answers:

- To decrease loading time of a web page
- To decrease number of round trips to a server

Re: Why does Share use javascript callbacks?

mikeh — Wed, 28 Mar 2012 08:59:01 GMT

Thanks - I'll try to clarify later this week when I can talk to the training team.

Thanks,
Mike

Re: Why does Share use javascript callbacks?

jpfi — Wed, 28 Mar 2012 10:20:58 GMT

yub, I was wondering about this question, too 😉
It's a question of definitions:

- round trip:
   - a) = full page reload?
   - b) = a HTTP round trip?

Ajax & callbacks should reduce the amount of a) but may increase the amount of b) (but smaller & faster requests…)

- web page loading time:
   - a) whole page rendering is completed
   - b) basic page rendering is completed & some parts may be still missing..
…
Cheers, Jan

Re: Why does Share use javascript callbacks?

mikeh — Thu, 29 Mar 2012 09:34:07 GMT

OK, I spoke to the training team about this question and I think it's worded correctly.

I had initially worried that the question was quite literally "Why does Share use javascript callbacks?" but in fact it talks about asynchronous HTTP requests being consumed by JavaScript in the form of callback functions. Jan is correct that this will actually *increase* the number of round-trip requests, but *does* make the initial page view render quicker. Data is populated from repo queries (in most cases) and rendered in-page, ensuring the user is not blocked from other UI interactions in the meantime.

I believe it's the "better user experience" angle that the question is aiming at.

Thanks,
Mike