Nick, On Tuesday, May 24, 2011 11:56:57 PM UTC+2, Nick Apperley wrote: > > Max - With regards to point 1 I did consider it but it isn't feasible > to use SSL for the entire website when large amounts of data is being > sent to/from the server. Most of the data being received from the > server is in JSON format, which although it is less verbose than XML > it does include other pieces of data that hasn't been requested from > the website (client). > > All of the received data comes from a DB as row(s). If a row contains > a foreign key then the referred row (by the key) is automatically > included instead of the key in a JSON file. This is automatically done > by the server, no changes were made to do this. You can imagine just > how much data is included if there is more than one foreign key, and > this automatically scales up recursively if the included row also > contains a foreign key.
I'm sorry, but how is this an argument against TLS, again? Cheers! Max -- 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.
