Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have already created my server in System.Net.WebSockets and now after transferring it between machines I had noticed Windows Server 2008 is not supported, are there any other implemetations which support an X509Certificate as authentication and would require minimal conversation.
I have been googling for this in the past 2 hours but haven't found anything meaningful, just a collection of poorly written, poorly documented libraries that throw exceptions on the regular, specifically SuperSocket, the server implementation of which seems to be complete buggy bull.
Could anyone post some sample client code from a decent library? I am growing desperate.
Frameworks include:
SignalR
XSockets
Super WebSocket
Alchemy WebSockets
Fleck
More options available via the realtime web tech guide
I know it is a little bit late, but I created a WebSocket C# implementation and it may be interesting for somebody.
There is also:
https://github.com/sta/websocket-sharp - sharp implements RFC6455 and is very popular amongst Unity3d developers
https://github.com/StackExchange/NetGain/ - stackoverflow's implementation of RFC6455
SignalR provides you a great way to add real-time features to your application. Under the hood, it uses either Web Sockets, Server-sent events, Long Polling or Forever Frames based on what the client and the server support. The coming version, scheduled to be released in the coming weeks, will support client-side (X509Certificate) certificates. You can refer to the following links for more details:
http://www.asp.net/signalr
https://github.com/SignalR/SignalR/wiki
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
There are similar questions but they seem to be pretty outdated; and hoping there might be a standard solution to this now.
Is there a standard library/framework that Java clients can use to consume .NET WCF services simply without any hassle setting up WSDL files; serializing/deserializing/parsing JSON files, or any of that?
How reliable would this be? I know I would have to ensure to keep consistent/similar data types between the 2 languages; but is there anything else that one might have to look out for when trying to implement this?
The java standard regarding Web services and RESTful are JAX-WS and JAX-RS in order. You can use any library that supports the above standards regardless of the server implementation technology.
Apache CXF, Jersey are few of the libraries that supports the above standards.
Apache CXF has wsdl2java tool which generates client for you. Netbeans, eclipse like IDEs have some Web service wizards which may create you the client in few clicks.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm looking for a library / framework that would allow me to easily achieve this:
Minimal message size (ideally something like - [16 bit message id] + [variable length message parameters]).
Needs as little plumbing code as possible.
TCP communication.
Handles dozens of connections easily.
Bidirectional communication.
I would like to use WCF-like approach, in which I would create contracts (operations and data) and would share that assembly with both clients and server. Or maybe there are some minimalistic bindings I could use - something even lighter than NetTcpBinding?
Lidgren.Network is a very simple library which is easy integrated to any project. I've tried it out a little and it's very easy to use. Give it a try.
http://code.google.com/p/lidgren-network-gen3/
You might wanted to check out Photon http://www.exitgames.com/
For the protocol format, I would look into Google's ProtoBuffers. There are numerous languages supported, including C#. The serialization is small, wicked fast, extendable, and easily upgraded version over version.
As far as transport is concerned this can be more difficult. Frankly .NET's WCF is not up to the task. Raw TCP/IP built on Sockets is difficult to manage properly. Even building upon the TcpListener can prove difficult but it is possible.
So what's a good way to go? Well that is difficult to answer given the bi-directional requirement. I'm not sure I can point to any one library and say it has the right answer. There are several available and all have their strengths and weaknesses. A lot is going to depend on more specific requirements of your project. Good luck ;)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I've seen quite a few examples of XMPP clients in .Net, and I've seen quite a few servers in various languages, but I'm looking for a .Net version (opensource if possible) of a XMPP server. It doesn't particularly have to be stable, or full of features, I just want something that works a little. Reliability is not really an issue.
Here are some that I found:
http://code.google.com/p/goodwarejabber/downloads/list (a bit old...)
EDIT: Note the comment below by the author of jabber-net, noting that jabber-net is not for writing servers:
http://code.google.com/p/jabber-net/wiki/FAQ_License
As an alternative, take a look at this SO question:
Jabber-net integration
or at these libraries:
http://code.google.com/p/jabber-net/
that would allow you to create your own (if that is an option for you).
You can download and take a look at trial version of MatriX library. It contains a sample on how to implement your own server.
http://www.ag-software.de/matrix-xmpp-sdk/download/
Download the MatriX for .NET version.
You could ask the support forum for help actually
http://forum.ag-software.de/
Coversant solution : SOAPBOX Server
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I saw a similar question from 1.5 years ago and I am hoping there is something better.
I am looking for a totally managed C# implementation because I need it for the .NET Microframework, so I can't have .NET wrappers around C code.
Has anyone run into a good C# implementation of the SIP protocol. I should not that I don't care about codecs, mostly will be dealing with call control.
My own C# SIP stack is at sipsorcery. It's far from perfect but as far as the RFC3261 core SIP standard goes it should be pretty good and you can hook into that using only SIPSorcery.Core assembly. The server applications can be disregarded if you're looking at doing some specialised call control.
I am using the ozeki voip sip sdk. It is written in c# and it provides a complete SIP implementation with all RFCs. The others I have tried were partial implementations only and didn't work with all my PBXs.
If you wish to be familiar with SIP protocol implementation then I suggest you to first read more useful information about the background of the VoIP technology. I used some examples for my project as well. I have found this explanation earlier:
The Session Initiation Protocol (SIP) is an IETF-defined signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol. SIP helps in establishing communication sessions which involve various media types such as audio, video, or collaborative multimedia.
I mean, SIP protocol is very important to use when we would like to build an audio or video based application. (For example: Ozeki VoIP SIP SDK is appropriate to create SIP VoIP call services.)
The info derives from this webpage: http://voip-sip-sdk.com/p_304-sip-protocol-implementation-voip.html. I always use this website because this SDK has the best documentation which is plain and transparent to understand it.
This .NET SIP SDK is probably the most comprehensive.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm porting old VB6 code that uses the Winsock control to C#. I haven't done any socket programming and I wonder if anyone has a good reference/tutorial/howto that I can use to start getting up to speed.
I'm appealing to the hive mind while I proceed with my generally unproductive googling.
I'm using UDP, not TCP at this time.
The August 2005 MSDN Magazine had an article about System.Net.Sockets and WinSock:
http://msdn.microsoft.com/en-us/magazine/cc300760.aspx
I recommend the asynchronous model for most applications, especially if you want performance or applications that don't hang as soon there is a network problem. For this the MSDN articles on Socket.BeginConnect and Socket.BeginReceive are good places to start.
The following link is not .NET, but many of the recommendations still hold: http://tangentsoft.net/wskfaq/articles/lame-list.html
MSDN is a good place to start
Are you working on:
a client (TCPClient)
or a server (TCPListener)
Just a heads up:
I would recommend first working with TCP rather than UDP. UDP doesn't automatically redeliver lost packets like TCP so it will add another element to the equation that will probably just confuse you as you're just starting out.
Building a socket client is relatively easy using the TCPClient class available in the .Net library. TCPListener is easy enough to use for a single client but if you're hoping to develop some server type application (IE: Handling multiple connections.) the real hurdle you'll have to overcome is understanding multithreading.
Once you've played around with single connection sockets I suggest you read up on multithreading.