locked
client - server - client architecture RRS feed

  • Question

  • User-820447932 posted

    Hi everybody,

    I'm going to create my own project, and i have some difficulties with technology selection.  I will have client application(windows forms) and web service. Data exchange between clients will be only by using this web service. Data will be like image stream, so I don't know which technology to use. I started to look at WCF, but i don't know a lot about it. Please, give an advice? Smile

    Tuesday, February 23, 2010 11:12 AM

Answers

  • User-1450380526 posted

    Well you are in rite direction, WCF is better option anyday
    You can have enormous enocding with all the binding, tcp http etc.

    SO you can choose tcp binding for your application as it is not a web application which is simiar to remoting

    I suggest you to practice a sample lab application for wcf if you don't have any idea about that
    here is the link to download the lab's

    http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=servicefactory&ReleaseId=7846

    there are so many, check which one suits you the best

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 12:40 AM
  • User-952121411 posted

    There is no question in my mind to use WCF based on your brief description of what you are doing.  I will admit though using both .asmx and WCF services over the years that the learning curve for WCF is much greater than that of .asmx web services.  I think the most cumbersome part of WCF is the configuration of the service and secondly the client (if any custom configurations on the client are needed after consuming the service).

    However the effort is worth it, and actually .asmx services are becoming more obsolete is some aspects.  For example WSE 3.0 used for many of the security enhancements for .asmx web services was not integrated past VS.NET 2005 for the inferred purpose of pushing people along to use WCF.  WSE 3.0 is also not being enhanced, nor will there be any new versions.

    Streaming with WCF is one of its strong points with lots of options.  I recommend looking to some of the following sites to help you get started with WCF.  Try your best to use fully functional examples as starting from scratch in a new technology like WCF can be difficult.  Take a look to the following:

    Windows Communication Foundation:

    http://msdn.microsoft.com/en-us/netframework/aa663324.aspx

    Introductory Videos:

    http://msdn.microsoft.com/en-us/netframework/first-steps-with-wcf.aspx

    Conceptual Overview:
     

    Hosting and Consuming WCF Services:

    http://msdn.microsoft.com/en-us/library/bb332338.aspx

    Large Data and Streaming:

    http://msdn.microsoft.com/en-us/library/ms733742.aspx

    How to: Enable Streaming:

    http://msdn.microsoft.com/en-us/library/ms789010.aspx

    Hope this helps! Smile

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 11:29 AM
  • User-820447932 posted

    Thanks for replies Wink 

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 12:29 PM

All replies

  • User-1450380526 posted

    Well you are in rite direction, WCF is better option anyday
    You can have enormous enocding with all the binding, tcp http etc.

    SO you can choose tcp binding for your application as it is not a web application which is simiar to remoting

    I suggest you to practice a sample lab application for wcf if you don't have any idea about that
    here is the link to download the lab's

    http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=servicefactory&ReleaseId=7846

    there are so many, check which one suits you the best

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 12:40 AM
  • User-952121411 posted

    There is no question in my mind to use WCF based on your brief description of what you are doing.  I will admit though using both .asmx and WCF services over the years that the learning curve for WCF is much greater than that of .asmx web services.  I think the most cumbersome part of WCF is the configuration of the service and secondly the client (if any custom configurations on the client are needed after consuming the service).

    However the effort is worth it, and actually .asmx services are becoming more obsolete is some aspects.  For example WSE 3.0 used for many of the security enhancements for .asmx web services was not integrated past VS.NET 2005 for the inferred purpose of pushing people along to use WCF.  WSE 3.0 is also not being enhanced, nor will there be any new versions.

    Streaming with WCF is one of its strong points with lots of options.  I recommend looking to some of the following sites to help you get started with WCF.  Try your best to use fully functional examples as starting from scratch in a new technology like WCF can be difficult.  Take a look to the following:

    Windows Communication Foundation:

    http://msdn.microsoft.com/en-us/netframework/aa663324.aspx

    Introductory Videos:

    http://msdn.microsoft.com/en-us/netframework/first-steps-with-wcf.aspx

    Conceptual Overview:
     

    Hosting and Consuming WCF Services:

    http://msdn.microsoft.com/en-us/library/bb332338.aspx

    Large Data and Streaming:

    http://msdn.microsoft.com/en-us/library/ms733742.aspx

    How to: Enable Streaming:

    http://msdn.microsoft.com/en-us/library/ms789010.aspx

    Hope this helps! Smile

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 11:29 AM
  • User-820447932 posted

    Thanks for replies Wink 

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, February 24, 2010 12:29 PM