I have gone through Jaeger Documentation. They have specified that how will Jaeger will work the HTTP request kind of scenario but if I want to get traces of Nservicebus's to publish/subscribe method then How will I get using Jaeger?
Is it possible? Or Jaeger only works with HTTP requests?
Not out of the box, you have to plug a behaviour into NSB that uses open telemetry
https://github.com/open-telemetry/opentelemetry-dotnet
You will have to write custom code.
Plus you can do push metrics as well as shown in our app insights, Prometheus and other samples.
Let's continue the conversation in our support channels?
Not sure if you are still looking for a solution for this. You should be able to do this currently using the NServiceBus.Extensions.Diagnostics.OpenTelemetry package from nuget. This is built by Jimmy Bogard and instruments NServiceBus with the required support for Open Telemetry.
The source for this is available here. You can connect this to any backend of your choice that supports Open Telemetry including but not limited to Jaeger and Zipkin.
Additionally, here is an example that shows this in action.
I want to program a simple GUI to connect to Yahoo! Protocol and act as a messengers which use them now. So, could any one describe Yahoo! Protocol structure ( Please help me in using of latest version of this protocol ).
Thanks about your attention.
I think you will find these links helpful as they describe several aspects the Yahoo! Protocol...
http://sourceforge.net/projects/ycs/
http://www.ycoderscookbook.com/
http://www.codeproject.com/KB/vb/YCC_Trainer.aspx
Yahoo Messenger Library C#
http://www.carbonize.co.uk/ymsg16.html
http://libyahoo2.sourceforge.net/
http://www.venkydude.com/articles/yahoo.htm
some general information http://en.wikipedia.org/wiki/Yahoo!_Messenger_Protocol
I am trying to create a client-server application that would communicate
using xml in a http format.
I already researched about client-server transferring file using TCP/IP.
It uses tcclient/tcplistener which worked very fine. However I was trying to
build an application that could use an http format of request to do the transferring of file.
I also had downloaded some codes for an implementation of an http server
but the http client needs to be a web browser, is there a way that I could just have a c# windows FORM as a client and pass those http webrequest/webresponse classes ?
Is there any suggestion that you can give?
Thank you very much in advance.
I hope you could help.
I think what you're doing here is basically reinventing Web Services. For .NET, you can either look at ASMX Web Services or at WCF.
I also think should have a look at Windows Communication Foundation, it gives a lot of possibilities, settings and security. I recommend the following books to read, that also helped me:
Professional WCF 4: Windows Communication Foundation with .NET 4
(Wrox Programmer to Programmer)
Programming WCF Services, Third Edition
Hope it helps you.
So,
I found that amazing thing called HTML5 WebSockets, new API. That is still in DRAFT version, but quite well supported. Full-duplex bi-directional communication. I know how to use it via JavaScript, there is APIs. But if I want to use a WebSocket client within my C#/.NET application, how to do that?
For example JavaScript: http://bohuco.net/blog/2010/07/html5-websockets-example/
Are there are any special client libraries for WebSockets in .NET?
sir
SuperWebSocket include a WebSocket server implementation and a WebSocket client implementation.
SuperWebSocket's project page
I've recently done some research into this whilst building a .NET and Silverlight client library for Pusher. I found the following WebSocket client libraries and projects:
Microsoft WebSocket client prototype
SuperWebSocket note: there is a client in there, it's just difficult to find
WebSocket-Sharp
Anaida
For the moment the Microsoft implementation is probably the easiest to use and it also has a Silverlight library. SuperWebSockets has a Silverlight project in the source but not in the latest drop.
Starting from .NET 4.5, WebSocket clients are supported via System.Net.WebSockets.ClientWebSocket
You can browse or download this sample C# app from MSDN Code website: http://code.msdn.microsoft.com/WebSockets-middle-tier-5b2972ce/sourcecode.
To the down-voters of the question, the sample is mainly focused on connecting to WebSocket services, which is another significant use-case for a network-centric C# application.
I haven´t tried the Microsoft implementation, but I think Xsockets has the fastest setup time (nuget package). Under 3 min from start to running a complete socketserver + client (demo chat application). Youtube demo
It has fallback to Silverlight and flash for older browsers.
You could use http://www.nuget.org/packages/Microsoft.AspNet.SignalR/ or http://www.asp.net/signalr
ASP.NET SignalR is a new library for ASP.NET developers that makes developing real-time web functionality easy. SignalR allows bi-directional communication between server and side. Servers can now push content to connected cliently instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.
A friend an I just released a very lightweight, lean, scalable C# websocket server: https://github.com/Olivine-Labs/Alchemy-Websockets
We built it to use in our online game, so our top concern was the quick and efficient handling of tons of connections. It's, from my research, the most efficient out there. And, as a bonus, it supports flash websockets as a fallback for users without websocket-enabled browsers.
If you're looking for a high performance enterprise WebSocket server, take a look at Kaazing. Kaazing has complete support for .NET including Xamarin.
Here is a step-by-step tutorial for AMQP: Checklist: Build Microsoft .NET AMQP Clients.
[Disclosure: I work for Kaazing.]
Yes, you will need an intermediary server which supports the WebSocket protocol. This server could be written in any language including .NET. Here's one for .NET but it really could be any language. As far as your site is concerned it could be ASP.NET and the client part in javascript which will talk to the WebSocket server.
I'm deploying XSockets.net. The framework works quite good, it is being maintained, the developers offer paid support but for normal issues they are also quite active here in SO and they help a lot.
They offer a .net API for implementing the sockets and also a javascript API for the client.
As a summary, I can recommend it.
You have a few choices
Roll your own - the spec is fairly simple
Use someone else's experimental version, such as this one C# Web socket server
Look into the MS WCF approach
I always wondered how to make an instance chat using ajax ! Ideas !? articles ?!
Thank you .
You basically just use AJAX to "subscribe" to messages pushed by a chat server. Then the client "publishes" messages which the server pushes to any clients subscribed to that channel.
NodeJS is great for instant ajax stuff like facebooks live feed or chat (Check out this open source example).
You can also give a look at the AjaxIM project which has a chat bar like facebook and has a NodeJS server and a PHP server (I suppose you could port that over to ASP.Net). I'd reccomend going with the NodeJS server and just use the javascript library to connect to it from your project.
A friend of mine released a project for helping to write the backend of such a feature, it's called the LiveChat Starter Kit and is available on CodePlex. I never tried it so can't comment on its use, but it have gathered some attention there. I think it's more curtailed to commercial websites for providing online support tough.
All that happens is that the javascript on the client uses ajax to send outgoing chat to the server, and the server uses ajax to send incoming chat to the client.
Of course there are a lot of different pieces involved but if you have questions about those, you should ask them.
I would suggest to use XMPP as it an open standard and quite a few implementations also available, following are some links which may help:
Ajax jabber/XMPP client recommendations (real experience only please) !
http://xmpp.org/
http://www.jabber.org/