I think this is due to the provision of core API compatibility. Due to this reason, all API has to be ported, now matter what. Take the case of URL and URI.
Nabeel On Tue, Jul 13, 2010 at 1:21 PM, guandalino <[email protected]> wrote: > Hi, GWT provides JRE emulation for both StringBuffer and > StringBuilder. The Java API says that in single threaded environments > the preferred choice is to use StringBuilder as it is faster. I also > remember to have read that browsers way to work is single threaded. > > So I'm wondering why and when one should use StringBuffer at all. Can > you clarify? > > Thank you. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
