Hi Heiko, Yes gwt-comet does leverage the GWT-RPC serialization mechanism. All you have to do is tell gwt-comet what types you want to send over the comet connection: http://code.google.com/p/gwt-comet/wiki/GettingStarted#Receiving_GWT_Seriali zed_Types No it does not depend on GWT-RPC's RemoteService interface, the Async version or the servlet implementing the remote service boilerplate. I'm also intending on supporting GWT 2.0's direct-eval RPC in the near future for faster more efficient serialization: http://code.google.com/p/google-web-toolkit/wiki/RpcDirectEval -----Original Message----- From: Heiko Braun [mailto:hbraun@redhat.com] Sent: Tuesday, 1 December 2009 8:09 PM To: Richard Zschech Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Errai comet implementation Hi Richard, thanks for pointing us to your project. I'll have a look and see to what degree we may rely on gwt-comet. One question upfront: You 'GWT serialization' of messages. Does that mean gwt-comet does leverage the serialization mechanism that are used with GWT-RPC? Does it depend on GWT-RPC, or did you find a way to decouple the actual marshalling/unmarshalling from GWT-RPC servlet boilerplate? Regards, Heiko On Nov 24, 2009, at 12:14 PM, Richard Zschech wrote: