|
|
You're in the
dotnet web services
group:new project - remoting, webservices or WCF?
dotnet web services:
We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large amounts of data may be sent to and from the client. My first thought was to use WCF but I was sad to learn that Framework 3 is not supported on Win 2k workstations, so that is unfortunately not an option :-( I like the better speed of _remoting_ over _webservices_, especially since we are talking about an intranet application. What technology would you recommend for a new project like this, starting today? I would like to be able to switch to WCF in the future when we no longer need to run the client on Win2k workstation. Would it perhaps be best to have the server expose separate kinds of "facades" so that a client can connect using either Remoting, asmx webservices or WCF (This would also require the client to be able to switch between these ways fo communication)? Advices on technology, and recommendations of good examples on the web, are greatly appreciated. Best Regards /KF
I should perhaps add that the server part of the application will run on a
Win 2003 server. [quoted text, click to view] "Kai Fransson" wrote:
> We're starting a new project with a distributed winform client that > communicates with a central server, primarily all on the same LAN. Large > amounts of data may be sent to and from the client. > > My first thought was to use WCF but I was sad to learn that Framework 3 is > not supported on Win 2k workstations, so that is unfortunately not an option > :-( > > I like the better speed of _remoting_ over _webservices_, especially since > we are talking about an intranet application. > > What technology would you recommend for a new project like this, starting > today? > > I would like to be able to switch to WCF in the future when we no longer > need to run the client on Win2k workstation. Would it perhaps be best to have > the server expose separate kinds of "facades" so that a client can connect > using either Remoting, asmx webservices or WCF (This would also require the > client to be able to switch between these ways fo communication)? > > Advices on technology, and recommendations of good examples on the web, are > greatly appreciated. > > Best Regards > /KF
Since you can't use WCF and you need to make this application today, I would
say that your choice of remoting vs. web services would then come down to the need for a proprietary/fast solution or the need for an non-proprietary/slightly slower solution. Today, it seems that you don't need to worry about a non-proprietary solution, so remoting would be fine, but what about the future? Will WCF save the day BEFORE you need to worry about scaling outside of the intranet? This is really all you need to think about. Converting a remoting app. to WCF should be no more troublesome that converting a web service app., so WCF wouldn't really factor into the decision making process. -Scott [quoted text, click to view] "Kai Fransson" <KaiFransson@discussions.microsoft.com> wrote in message news:F4E4D192-03AB-49EA-AB4D-614A3C9D6858@microsoft.com... >I should perhaps add that the server part of the application will run on a > Win 2003 server. > > > "Kai Fransson" wrote: > >> We're starting a new project with a distributed winform client that >> communicates with a central server, primarily all on the same LAN. Large >> amounts of data may be sent to and from the client. >> >> My first thought was to use WCF but I was sad to learn that Framework 3 >> is >> not supported on Win 2k workstations, so that is unfortunately not an >> option >> :-( >> >> I like the better speed of _remoting_ over _webservices_, especially >> since >> we are talking about an intranet application. >> >> What technology would you recommend for a new project like this, starting >> today? >> >> I would like to be able to switch to WCF in the future when we no longer >> need to run the client on Win2k workstation. Would it perhaps be best to >> have >> the server expose separate kinds of "facades" so that a client can >> connect >> using either Remoting, asmx webservices or WCF (This would also require >> the >> client to be able to switch between these ways fo communication)? >> >> Advices on technology, and recommendations of good examples on the web, >> are >> greatly appreciated. >> >> Best Regards >> /KF >>
I read somewhere that you can expose more than one endpoint from your WCF
service, so that clients running win2000 can also communicate with your WCF service. Is this worthwhile, or should I just build a classic remoting app and then convert it to WCF when the time comes? Also, any good reading or samples would be appreciated. /Kai [quoted text, click to view] "Scott M." wrote:
> Since you can't use WCF and you need to make this application today, I would > say that your choice of remoting vs. web services would then come down to > the need for a proprietary/fast solution or the need for an > non-proprietary/slightly slower solution. > > Today, it seems that you don't need to worry about a non-proprietary > solution, so remoting would be fine, but what about the future? Will WCF > save the day BEFORE you need to worry about scaling outside of the intranet? > This is really all you need to think about. Converting a remoting app. to > WCF should be no more troublesome that converting a web service app., so WCF > wouldn't really factor into the decision making process. > > -Scott > > > "Kai Fransson" <KaiFransson@discussions.microsoft.com> wrote in message > news:F4E4D192-03AB-49EA-AB4D-614A3C9D6858@microsoft.com... > >I should perhaps add that the server part of the application will run on a > > Win 2003 server. > > > > > > "Kai Fransson" wrote: > > > >> We're starting a new project with a distributed winform client that > >> communicates with a central server, primarily all on the same LAN. Large > >> amounts of data may be sent to and from the client. > >> > >> My first thought was to use WCF but I was sad to learn that Framework 3 > >> is > >> not supported on Win 2k workstations, so that is unfortunately not an > >> option > >> :-( > >> > >> I like the better speed of _remoting_ over _webservices_, especially > >> since > >> we are talking about an intranet application. > >> > >> What technology would you recommend for a new project like this, starting > >> today? > >> > >> I would like to be able to switch to WCF in the future when we no longer > >> need to run the client on Win2k workstation. Would it perhaps be best to > >> have > >> the server expose separate kinds of "facades" so that a client can > >> connect > >> using either Remoting, asmx webservices or WCF (This would also require > >> the > >> client to be able to switch between these ways fo communication)? > >> > >> Advices on technology, and recommendations of good examples on the web, > >> are > >> greatly appreciated. > >> > >> Best Regards > >> /KF > >> > >
Traditionally we've used Com+ Enterprise Services for scalability and
transaction handling. Do you have any recommendations for achieving this using WCF? Most examples I find host their WCF services in a console app, which cannot be best practice for creating a facade for my server application. Is a windows service a good facade for my server application? Any advice is greatly appreciated. /Kai [quoted text, click to view] "Spam Catcher" wrote:
> =?Utf-8?B?S2FpIEZyYW5zc29u?= <KaiFransson@discussions.microsoft.com> > wrote in news:4C7FAE44-E774-4FFC-B9EE-9C324BAF4E1B@microsoft.com: > > > I read somewhere that you can expose more than one endpoint from your > > WCF service, so that clients running win2000 can also communicate with > > your WCF service. Is this worthwhile, or should I just build a classic > > remoting app and then convert it to WCF when the time comes? > > Yup true - you can still use WCF - but just use the web service channel.
=?Utf-8?B?S2FpIEZyYW5zc29u?= <KaiFransson@discussions.microsoft.com>
wrote in news:4C7FAE44-E774-4FFC-B9EE-9C324BAF4E1B@microsoft.com: [quoted text, click to view] > I read somewhere that you can expose more than one endpoint from your > WCF service, so that clients running win2000 can also communicate with > your WCF service. Is this worthwhile, or should I just build a classic > remoting app and then convert it to WCF when the time comes?
=?Utf-8?B?S2FpIEZyYW5zc29u?= <KaiFransson@discussions.microsoft.com>
wrote in news:2CA5D3AB-A4BB-466A-B472-CBA70496A84B@microsoft.com: [quoted text, click to view] > Traditionally we've used Com+ Enterprise Services for scalability and > transaction handling. Do you have any recommendations for achieving > this using WCF? Here you go: http://msdn2.microsoft.com/en-us/library/bb735856.aspx FYI, .NET 2.0 and WCF has transactional support - so perhaps it might be good enough without resorting to COM+. [quoted text, click to view] > Most examples I find host their WCF services in a console app, which > cannot be best practice for creating a facade for my server > application. Is a windows service a good facade for my server > application? Any advice is greatly appreciated. Absolutely. Console App vs. Windows Form vs. Services is all schematics. The underlying syntax is identical across the board... and the way WCF
Hi Fransson,
My project also same like this. Let me know whether i can use the WCF or Remorting? Can you guide me abt this? Regards, RAJA [quoted text, click to view] "Kai Fransson" wrote:
> We're starting a new project with a distributed winform client that > communicates with a central server, primarily all on the same LAN. Large > amounts of data may be sent to and from the client. > > My first thought was to use WCF but I was sad to learn that Framework 3 is > not supported on Win 2k workstations, so that is unfortunately not an option > :-( > > I like the better speed of _remoting_ over _webservices_, especially since > we are talking about an intranet application. > > What technology would you recommend for a new project like this, starting > today? > > I would like to be able to switch to WCF in the future when we no longer > need to run the client on Win2k workstation. Would it perhaps be best to have > the server expose separate kinds of "facades" so that a client can connect > using either Remoting, asmx webservices or WCF (This would also require the > client to be able to switch between these ways fo communication)? > > Advices on technology, and recommendations of good examples on the web, are > greatly appreciated. > > Best Regards > /KF
I think if you read the other posts in this thread, you'll have your answer.
[quoted text, click to view] "RAJA" <RAJA@discussions.microsoft.com> wrote in message news:C64C5FF6-64BB-42F2-8129-918CF6018CFE@microsoft.com... > Hi Fransson, > > My project also same like this. Let me know whether i can use the WCF or > Remorting? Can you guide me abt this? > > Regards, > RAJA > > "Kai Fransson" wrote: > >> We're starting a new project with a distributed winform client that >> communicates with a central server, primarily all on the same LAN. Large >> amounts of data may be sent to and from the client. >> >> My first thought was to use WCF but I was sad to learn that Framework 3 >> is >> not supported on Win 2k workstations, so that is unfortunately not an >> option >> :-( >> >> I like the better speed of _remoting_ over _webservices_, especially >> since >> we are talking about an intranet application. >> >> What technology would you recommend for a new project like this, starting >> today? >> >> I would like to be able to switch to WCF in the future when we no longer >> need to run the client on Win2k workstation. Would it perhaps be best to >> have >> the server expose separate kinds of "facades" so that a client can >> connect >> using either Remoting, asmx webservices or WCF (This would also require >> the >> client to be able to switch between these ways fo communication)? >> >> Advices on technology, and recommendations of good examples on the web, >> are >> greatly appreciated. >> >> Best Regards >> /KF >>
Thanks. I'll check it.
[quoted text, click to view] "Scott M." wrote:
> I think if you read the other posts in this thread, you'll have your answer. > > > > "RAJA" <RAJA@discussions.microsoft.com> wrote in message > news:C64C5FF6-64BB-42F2-8129-918CF6018CFE@microsoft.com... > > Hi Fransson, > > > > My project also same like this. Let me know whether i can use the WCF or > > Remorting? Can you guide me abt this? > > > > Regards, > > RAJA > > > > "Kai Fransson" wrote: > > > >> We're starting a new project with a distributed winform client that > >> communicates with a central server, primarily all on the same LAN. Large > >> amounts of data may be sent to and from the client. > >> > >> My first thought was to use WCF but I was sad to learn that Framework 3 > >> is > >> not supported on Win 2k workstations, so that is unfortunately not an > >> option > >> :-( > >> > >> I like the better speed of _remoting_ over _webservices_, especially > >> since > >> we are talking about an intranet application. > >> > >> What technology would you recommend for a new project like this, starting > >> today? > >> > >> I would like to be able to switch to WCF in the future when we no longer > >> need to run the client on Win2k workstation. Would it perhaps be best to > >> have > >> the server expose separate kinds of "facades" so that a client can > >> connect > >> using either Remoting, asmx webservices or WCF (This would also require > >> the > >> client to be able to switch between these ways fo communication)? > >> > >> Advices on technology, and recommendations of good examples on the web, > >> are > >> greatly appreciated. > >> > >> Best Regards > >> /KF > >> > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |