"Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message
news:zmNEZXSYHHA.3680@TK2MSFTNGHUB02.phx.gbl...
> Hello Hao,
>
> Regarding on your application scenario, since the electric devices are of
> different heterogenous platform, therefore, normally we have two
> considerable approachs:
>
> 1. Use raw socket and deine your own communication protocol to transfer
> data between client and server application.
>
> 2. Use interopable XML webservice to transfer data
>
> For WCF, it does support XML webservice conform interface/endpoint,
> however, to make the webservice communiation interopable, you need to use
> basic http protocol/channel. The problem here is that XML webservice over
> http will always transfer data in plain XML text format. Thus, any binary
> data will need to be encoded and decoded at webservice's server/client
> side. Also, such binary-XML encoding will increase the size of the
> payload.
> So for your case, as you said the operations would be performed
> frequently, I suggest you still keep using the socket approach.
>
> If you have any further questions or any other concerns, please feel free
> to post here.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> ==================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

"Hao" wrote:

> I understand and completly agree that socket programming is the most
> efficient. Of cause the web service is more open to third party components
> and are easier to integrate.
> We already spent about a year building and released a new server using web
> service to transfer data between .Net and Windows/Linux gsoap engines from
> all devices. It works for small to medium data load. We are now
> re-architecture because we realized the network traffic is usually
> overloaded. Before we go back to sock programming, which we have to develop
> our own protocol, we want to know if HTTP compression is valuable in
> compacting data? Our data is alreasy strongly typed by gsoap in all devices.
> Does WCF support compression? What is the typicall HTTP compression rate? A
> lot of our data are strings and floats.
> Thanks.
> Hao
>
> "Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message
> news:zmNEZXSYHHA.3680@TK2MSFTNGHUB02.phx.gbl...
> > Hello Hao,
> >
> > Regarding on your application scenario, since the electric devices are of
> > different heterogenous platform, therefore, normally we have two
> > considerable approachs:
> >
> > 1. Use raw socket and deine your own communication protocol to transfer
> > data between client and server application.
> >
> > 2. Use interopable XML webservice to transfer data
> >
> > For WCF, it does support XML webservice conform interface/endpoint,
> > however, to make the webservice communiation interopable, you need to use
> > basic http protocol/channel. The problem here is that XML webservice over
> > http will always transfer data in plain XML text format. Thus, any binary
> > data will need to be encoded and decoded at webservice's server/client
> > side. Also, such binary-XML encoding will increase the size of the
> > payload.
> > So for your case, as you said the operations would be performed
> > frequently, I suggest you still keep using the socket approach.
> >
> > If you have any further questions or any other concerns, please feel free
> > to post here.
> >
> > Sincerely,
> >
> > Steven Cheng
> >
> > Microsoft MSDN Online Support Lead
> >
> >
> >
> > ==================================================
> >
> > Get notification to my posts through email? Please refer to
> > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> > ications.
> >
> >
> >
> > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > where an initial response from the community or a Microsoft Support
> > Engineer within 1 business day is acceptable. Please note that each follow
> > up response may take approximately 2 business days as the support
> > professional working with you may need further investigation to reach the
> > most efficient resolution. The offering is not appropriate for situations
> > that require urgent, real-time or phone-based interactions or complex
> > project analysis and dump analysis issues. Issues of this nature are best
> > handled working with a dedicated Microsoft Support Engineer by contacting
> > Microsoft Customer Support Services (CSS) at
> > http://msdn.microsoft.com/subscriptions/support/default.aspx.
> >
> > ==================================================
> >
> >
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
>
>