I'm currently trying to understand what the best approach to implement a solution is when I have a Java page that has to invoke a Java service and render content on the page.
(The solution has a limited scope so please do not mention here alternative solutions with other frameworks such as JSF, Spring, etc....).
Scenario....: PAGE, Server-side logic reading a XML config file (no database).
> The number of requests my server-side logic that has to receive the HTTP request and reads the configuration file is : 35 millions yearly.
XML data (payload) to be parsed by the browser would not be larger than 20-50KB
> This solution seems to be much clearer by delivering loose-coupling without overloading the browser with client-side processing.
> However it seems that I can only run the Java custom tags on Java pages, it's not my situation
I'm now working on the advantages and disadvantages of both solutions...have here different pros and cons...could you please give me your insight regarding the ones you think that are the most important to be taken into account here ? (I will not post them here because I don't want to influence your answers) I need to hear from you
1 - With the JS solution, one of the main advantages here is that I can benefit from the Asynchronous calls without impacting the page loading as well as the response time. Is it true?
3- If my page is not a Java page, would there be any way to run the Custom tag? (IFRAME?)
4- What approach do you use with Custom Tags/Tag Handler implementations to see whether it's performing well ?
5- Considering the situation where I mentioned that my page that executes the Custom that might be in another server/domain than my Tag Handler, I need to understand:
- What is the protocol of communication between my custom tag and the Tag handler?