Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / August 2005

Tip: Looking for answers? Try searching our database.

Web service design question

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
James - 23 Aug 2005 03:57 GMT
Under IIS 6, what would be the suggested approach of a .net web service
calling a backend socket server that would handle a high transaction volume?
Can I just create the socket, send the data, receive the response and close
the socket in the webMethod? Should I create a pool of socket connections?
I'm really looking for some design suggestions?
Allen St.Clair - 23 Aug 2005 05:52 GMT
Yes, you can.
Most of functions, like Threading, Socket are usable in ASPX too.

> Under IIS 6, what would be the suggested approach of a .net web service
> calling a backend socket server that would handle a high transaction
[quoted text clipped - 3 lines]
> the socket in the webMethod? Should I create a pool of socket connections?
> I'm really looking for some design suggestions?

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.