As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am trying to develop web chat integrated to site on ASP.NET. What technology for messaging is better to use for it? Please tell about benefits or disadvantages of each other.
I will be very glad to each answer. I incline to using SignalR.
I wouldn't include WCF just for the fact that it is more of a technology for building services that serve the data you want.
So it really boils down to websockets and SignalR.
websockets are a techonolgy to allow bi-directional communication in a web environment. Of course it isn't supported by all browsers.
SignalR is a library the rolls multiple communication technologies together. EG: websockets & long-polling. It is the better choice for your question as it will automatically take care of the technology that can be used to accomplish the bi-directional communication you seek.
WCF is for tick-client apps; it is not designed to be consumed from a browser.
Signalr is a wrapper around web sockets (with fallbacks) and is what you want to use
WebSockets is a protocol with various implementations in different languages.
For non-real-time scenarios, you would want ASP.Net Web API.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I would like to make an app that get data from web site for windows 8 Metro which I already have a couple of offline apps there ,but I really don't have an idea where to start and what to study to know with online applications.
Should I learn WCF or ASP.Net or something else?
I know this didn't work with Metro but I just wanna to learn the best way to work with servers from an app.
My programming language is C#.
Thnx.
WCF is overkill and is on the way out anyway - SOAP is dead, long-live REST!
Anyway, depending on what web-service you want to talk to you can use either a pre-written client or write your own. If it's a RESTful service then you can easily write your own client using HttpWebRequest, if it's a SOAP/WCF service then you'll probably want to use VS's client proxy generator to save you the pain.
...and yes, all this works with Metro (or rather, Tifkam) because you can do it in pure C# using classes made available to these kinds of applications.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am following this guide here. P2P
One of the advantages I had thought P2P would bring is the fact that it is a serverless setup.
Now that I have this working I noticed that you do need a resolver to keep track of who is connected.
To me this is really does require a server as you need a resolver to make P2P work in the first place.
Ami missing something?
It depends on your definition of a server I suppose. Using a P2P game for example most players will connect to a central point, be matched up and will then communicate between themselves with no involvement from the server.
This means the server doesn't have to host any data it simply has to coordinate those who do. It keeps resources down (as each client only needs to connect once) and the infrastructure is often more robust.
Do you need a central application to coordinate peers? Yes
Does that application need to stream content/data to each peer? No
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What are some actual, realistic situations that one would need to use raw socket programming over WCF? I know performance is one, but are there any others?
There may be situations where you are talking to a third party system that requires communication via sockets (we have to with one).
When the software at the other end of the connection knows nothing about .NET or WCF - the WCF netTcpBinding assumes both ends are implemented using WCF.
say you need to send receive commands from a external device which does not support WCF communication.
Say you would want to pass some commands to a device connected to your serial port.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is SOA (in the .net world) mostly a design strategy on building a application that brings together various endpoints?
i.e. a web service layer (WCF) allows for different clients to connect and consume services, MSMQ is used to provide reliable messaging and consuming in a transaction manner.
Would love a real world 'human' answer to this with specific technologies used/patters etc.
SOA is a design pattern that aims to create components in your system as loosely-coupled services that collaborate with one another. It is a natural extension of object-oriented programming (applied at the system level) and is not technology specific.
WCF is a technology that makes implementing an SOA easier in .NET by providing a simple abstraction over common messsage transport mechanisms and allow those services to talk to one another. Note if you are using web services as the underlying mechanism the endpoints don't even need to both be .NET
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Hey guys, I'm starting the development of a native iPhone app which will implement a chat interface. So far the implementation seems to be pretty complicated, I've read of Websockets, XMPP/Jabber and raw TCP/IP sockets, but have no idea which to use. The client will be programmed in Objective-C, and I would like to program the server in C# (and not have to pay $100/month for a hosting service).
What would you guys suggest?
I would suggest using something like XMPP/Jabber as there are already a ton of libraries in existence for pretty much every language under the sun. That would allow you to focus on the unique aspects of your app rather than having to worry about implementing a protocol. Check out the XMPP website for a list of libraries for both clients and servers.
With regards to hosting, C# might be difficult to find free hosting simply because it requires a Windows installation which requires a non-free license. You can find cheap Windows hosting through somebody like GoDaddy, but you won't be able to find free (at least I doubt it).