TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
NR
NA
3
0
Remoting vs Sockets
Jul 8 2008 2:47 AM
Hi,
I'm building an application for versioning purpose.
Though this versioning system is different from our regular software versioning applications like WinCvs, VSS etc (as my versioning system has more of the domain essence to it), the basic architecture would still remain same.
There is our client application containing some versionable elements, from which we trigger new versions, which would be stored in a repository at a server.
Here I'm stuck with the communication channel. I've figured out 2 ways of doing it
1. Using sockets
2. Remoting
Primarily there is only transfer of files involved between the client and the server.
I'd like to know which is the better way to go about it.
Also is there any other approach apart from remoting and sockets to form a client - server app with this kind of requirements?
Thanks in advance
Naren
Reply
Answers (
2
)
SilverLight Beta 2
Communicating with database