All nonsense... Interface design comes down to skill and decent designers - SIMS.net is not the worlds best interface and could very easily be implemented as a web interface. Browser requirements would just be like any other requirement (ie. SIMS.net requires .Net v2, so a web app could require IE7), or it could simply be written in any of the cross browser capable languages. And integration all depends on how you do it. If it is done via ActiveX controls then it can integrate just fine. If they are just discussing things like the reports then why not use industry standard export types?
Originally Posted by mark
Welcome to 2007... Technologies such as AJAX have been around for a good few years.
· Each time the user requests data from the server, the entire screen is
resent back to the client application along with the data requested. This
requires a higher bandwidth than a clientserver application which only
requires the data itself.
Wow, absolute tosh. Have they not heard of XML? And compression can take place just fine...
· Browsers use HTML to describe their screens and data content. This
protocol is uncompressed and text based which is part of its strength;
but it is also a very inefficient protocol for transmitting data and screen
descriptions. In addition to this the server cannot carry out the kind of
clever compression algorithms used in Thin Client configurations
because browsers aren’t equipped to cope with partial or compressed
Huh? So the single SIMS server situation is not centralised? This is more rubbish.
· There is a single server within the network generating screen layouts
and integrating them with the requested data, for every user, in
response to every request, on an ad-hoc basis. This over-centralisation
can lead to tricky deployment (an Internet server is required) and
requires further load balancing between the internet server and the
Rubbish. That's all I can say on this really!
Browser based applications are best used when one of the following is needed
1. Anonymous access where the user doesn’t have or doesn’t want to
install the application software (as is the case with Parents Gateway).
2. The destination operating systems cannot be known by the system
Recent developments mean that it is possible that the future of internet browsers as an application hosting environment may be narrowed even further to that subset of applications designed for use by the public on the public internet.
Well I have to say that that was the most ignorant and useless pile of nonsense going. It is based on concepts that are at least a decade old and seems to be written by someone who has absolutely no knowledge of web technologies. Why am I not surprised though?