> Let me summarize: what you want is... Java applets, Silverlight, Flash/ > Flex, with a way to do "server push". Well, you already have all this: > Silverlight can use sockets [1], as well as Flash/Flex [2] (I don't > know for Java/JavaFX, but as far as I'm concerned java on the web is > dead for a long time (except on the server side)). > If you want some form of "standard protocol" to transport typed > values, instead of plain old binary sockets, you can implement > WebSockets (or any other protocol) on top of them. > Thanks for adding to the discussion, but ...
•As I have already said in several different ways, I know that there are "solutions" to the challenges I have mentioned. But as Célio pointed out, they are all kludges. We have constructed a huge Rube- Golberg machine to crack an egg. That's what originally started me thinking about this new browser idea. • Manipulating pull to simulate push is not the same as push. • Sockets/ports can be blocked. But as I said earlier, hardly anyone blocks port 80. If we had a standard port for serving application that allowed push communication, you wouldn't have to worry about it being blocked. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
