> I believe it is. In my understanding, having a browser listen on a > specific port and having it wait for any incoming connection from > anyone exposes it to attacks.
Hi Yanick, I think you are misunderstanding push communication. When you use a chat program (outside of the web), push is being used. It's not that your browser would be sitting there listening for anything pushed it's way, and would accept anything. But when you connected to a specific application, you would be opening a connection with that server. You would be connecting because you were expecting information to be pushed back to you. And when you disconnected, the connection would be terminated. I'm sorry, but making a blanket statement that push is evil is unfair. Your thoughts about overloading connections is a valid concern, but like I said, it's not like push is not already being used - just not on the web. I think that the issues could be resolved. And as to your security concerns, yes, there would need to be care taken in order to insure that the new network was secure. But I firmly believe that, given proper thought, security would not be a problem - certainly not any MORE that the existing web. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
