SWA - Why Java?
Posted: Wed Dec 07, 2005 9:16 pm
Why is the web client Java?
If you look at OWA or Gmail or any of the newer web clients for other solutions, they're turning to AJAX (I hate to use a buzzword) for a cross-platform browser solution. While it's true that Microsoft intentionally cripples OWA for non-MSIE browers, it is not true of the other AJAX clients as there is no technical reason to do so. If you look at the other solutions, you can see that they support dragondrops (read it aloud ;) and context menus (well, gmail doesn't to be fair) just as one would expect from a thick client.
Why do I suggest this? Because in my brief testing of Scalix (we have not cut over to it - we're in a "wait and see" pattern until the next Scalix release) I have found the Ajax client to be slow to run on still-useful Pentium III and slower Pentium 4 workstations - and downright painful on dual processor Pentium II Xeon workstations with 1GB RAM. Also, the Java client does not seem to run in konqueror, neither in KDE 3.4.2 nor in KDE 3.5.0
If you look at OWA or Gmail or any of the newer web clients for other solutions, they're turning to AJAX (I hate to use a buzzword) for a cross-platform browser solution. While it's true that Microsoft intentionally cripples OWA for non-MSIE browers, it is not true of the other AJAX clients as there is no technical reason to do so. If you look at the other solutions, you can see that they support dragondrops (read it aloud ;) and context menus (well, gmail doesn't to be fair) just as one would expect from a thick client.
Why do I suggest this? Because in my brief testing of Scalix (we have not cut over to it - we're in a "wait and see" pattern until the next Scalix release) I have found the Ajax client to be slow to run on still-useful Pentium III and slower Pentium 4 workstations - and downright painful on dual processor Pentium II Xeon workstations with 1GB RAM. Also, the Java client does not seem to run in konqueror, neither in KDE 3.4.2 nor in KDE 3.5.0