Totally agree. Remoting the widgets is a big win for usability through improved bandwidth and perceived latency. X, Citrix and m$ terminal server all end up doing painfully too much. The remote widget approach wins handsomely at the scalability stakes which is always handy if you think you might have customers one day;-)
I would like to see a wxWin, qt or GTK remote. Is the qt netscape/ie plug-in such a beast already? When encapsulated as a browser, I hear this approach called a metabrowser.
Bullant use this remote widget idiom in their remote player which is kind of neat. You can see this idiom in action through their developer site at http://www.bullant.com if you download their player.
Remoting the UI via Berlin's kind of approach will lead to improved UI with better scalability. Great if you want to vulture capitalise your ASP model. Even better if you want to use an ASP.
An image is still an image and bandwidth gets clobbered no matter what.
Slashdot Mirror
Totally agree. Remoting the widgets is a big win for usability through improved bandwidth and perceived latency. X, Citrix and m$ terminal server all end up doing painfully too much. The remote widget approach wins handsomely at the scalability stakes which is always handy if you think you might have customers one day ;-)
I would like to see a wxWin, qt or GTK remote. Is the qt netscape/ie plug-in such a beast already? When encapsulated as a browser, I hear this approach called a metabrowser.
Bullant use this remote widget idiom in their remote player which is kind of neat. You can see this idiom in action through their developer site at http://www.bullant.com if you download their player.
Remoting the UI via Berlin's kind of approach will lead to improved UI with better scalability. Great if you want to vulture capitalise your ASP model. Even better if you want to use an ASP.
An image is still an image and bandwidth gets clobbered no matter what.
matt hurd.
perception is reality