Frequently Answers & Questions
Search the FAQ Search
FAQ Frequently Asked Questions.

Found 14 entries

Questions:

Are Ajax applications easier to develop than traditional web applications?
Do Ajax applications always deliver a better experience than traditional web applications?
Do QuariX applications need to have Flash installed at the client side?
Do QuariX applications need to have Java installed at the client side?
Does Ajax have significant accessibility or browser compatibility limitations? Do Ajax applications break the back button? Is Ajax compatible with REST? Are there security considerations with Ajax development? Can Ajax applications be made to work for use
How much freedom there is in designing QuariX applications?
Some of the applications based on Ajax don't use XML at all. Do I have to use XML and/or XSLT in an Ajax application?
We've seen a number of technologies evolve in the past 10 years that help make the web user's experience more dynamic, including JavaScript and Dynamic HTML (DHTML). Is AJAX better than what we had before?
What happens if someone needs components that are not yet available in QuariX?
What happens with the 10% of the user that have JavaScript disabled?
What operation systems are needed for the server part of QuariX?
What Web servers are needed for QuariX?
What's the big deal about AJAX? Why all the buzz?
Which are the strong points of Ajax?

Click on question to see answers

XfaQ v.1.1_mgfi by MGFi