multipart/x-mixed-replace performs better, but why wave.google.com does not use?
On 12月21日, 下午12时50分, Tad Glines <[email protected]> wrote: > The client/server protocol in WiaB originally only used WebSockets for > transport. This limited the set of browsers that could be used with WiaB. I > added support for Socket.IO which is has similar semantics but works with a > lot more browsers. It uses multipart/x-mixed-replace if the browser supports > it. > > While there is some relation between the wave.google.com client/server > protocol and that used in WiaB, they are not the same and > use completely different transports. > > -Tad > > On Mon, Dec 20, 2010 at 7:13 PM, u20024804 <[email protected]> wrote: > > rt > > > why? > > > and are they are more difference ? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Wave Protocol" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<wave-protocol%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/wave-protocol?hl=en. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
