The only related issue I could find about this was originally slated to be included as far back as GWT 1.4, but still hasn't made it in.
(https://code.google.com/p/google-web-toolkit/issues/detail?id=604)
What would it take for GWT to emulate InputStream/OutputStream/ByteArrayInputStream/ByteArrayOutputStream, etc?
Naturally, FileInputStream/FileOuputStream are out of the question, but having much of the rest of java.io available client-side would be very useful. It would also help for certain cases where duplicate code must be maintained for the client-side, as well as the server-side, just to avoid such emulation issues. Nobody likes having to maintain duplicate code.
-- (https://code.google.com/p/google-web-toolkit/issues/detail?id=604)
What would it take for GWT to emulate InputStream/OutputStream/ByteArrayInputStream/ByteArrayOutputStream, etc?
Naturally, FileInputStream/FileOuputStream are out of the question, but having much of the rest of java.io available client-side would be very useful. It would also help for certain cases where duplicate code must be maintained for the client-side, as well as the server-side, just to avoid such emulation issues. Nobody likes having to maintain duplicate code.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment