Please allow ads on our site
LoginTechnology choice for a service that .NET 2.0 clients will consume
General Tech Technology & Software 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Similar Forum
Explore Other Libraries
Online Exams
Question Bank
Career News
Feeds
Full Forms
Dictionary
Interview Question
Gigs
Quotes
Lyrics
Videos
Courses
Blogs
Tutorials
Forum
Educators
Corporates
Tools
manpreet![Tuteehub forum best answer]()
Best Answer
3 years ago
I am trying to decide which technology to use to implement a service that will be consumed by .NET 2.0 clients.
The client needs to be able to request a set of files. The request will consist of filename and version. The number of files a client may request can vary.
The clients must not be expcted to support .NET above version 2.0.
The service will stream the requested set of files as a single compressed archive.
I am somewhat baffled regarding the choices I have in which to implement the service and (more importantly) how to consume the service from .NET 2.0. It's been a long time since I wrote .NET 2.0 code and I'm not sure how to consume any of the technologies I have been reading about from .NET 2.0 code.
I believe my options with regards to technology are:
Which of the above are viable for .NET 2.0 clients?
How can I pass my set of filename/version mappings to from .NET 2.0 code?
I don't need exact code; just a general recommendation for the service technology and a general idea of how to pass my data up. I can research the rest myself.