Hi jon918,
Please see my replies inlined below:
1) In 1.5 there is now support for managing the serialization using
the SerializationStreamFactory on the client. However on the server, I
don't see how I can retrieve the SerializationPolicy for my module
without using a GWT RPC call. Must I use the default serialization
policy to take advantage of this feature?
The serialization policy file is generated as a security measure to make
sure that types you're sending across the wire are indeed the ones you
intended to deserialize when they come back to the server.
If you're using the SerializationStreamFactory on the client-side for custom
serialization, I would imagine that you're either using a non-Java backend
or doing something interesting with a Java backend. In case it's the former,
you shouldn't need to worry about the serialization policy file and instead
add extra security considerations around whatever is deserializing code on
the server-side. If you are using a Java backend, is there any reason why
you can't use GWT RPC with a mix of custom field serializers as needed for
any special needs?
Basically, more information on what you're trying to do here would give us
more to go on about why / how you need to get the serialization policy file
while using non standard GWT RPC.
2) RpcServletUtils.writeResponse double-buffers the output when it
gzip's the response payload. Why is this done instead of writing
directly to the response output stream? Is sending the content length
critical for some reason?
I'll have to check on this one and get back to you. I don't think that
sending the content-length is terribly important, however it could be useful
for things like download progress notifications and so on.
3) Are there plans to open up the RPC APIs more than they are today in
general.
I believe that making GWT APIs refactored and opened up has been and will be
an iterative process. We've had some major improvements in the linker
subsystem (now refactored and pluggable) as well as improvements in GWT RPC
(such as the refactored SerializationStreamFactory).
I think it's safe to say that you can look to better and better designs to
make the GWT APIs more easy to extend and modify.
Hope that helps,
-Sumit Chandel
Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
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
-~--~~~~--~~--~--~---
