I have a requirement for web application developed in asp.net which allows users to make voice calls among each other from the website.
I have looked at api of skype but it seems more inclined towards desktop application. IS there any api which supports for web application like gtalk etc.
Which technology could be best used for developing such kind of applications? Any input, references would be helpful.
I did read that jabber is underlying technology for gtalk. Does jabber support voice calls, and would it be useful for my situation?
If you can include Flash, it has API for that job, but for client side layer only... probably you can chose java/.net for server side.
The only solution here is flash. Gmail / Gtalk requires the user to download a plugin for it to work, so technically it is a windows application being called from a webpage.
I recommend flash and asp.net for the backend, as said above. Either that or if you are OK with deploying plugins, you could go that route. I wouldn't recommend it unless it is internal only.
Related
I am new to WCF and going through tutorials right now. I was wondering what are the benefits and disadvantages of using a WPF or an ASP.NET web application as a client for a service. I understand it will depend on the kind of service, but besides the common difference of one being a windows app and other a web application, what are the advantages of one over other.
First of all, the choice of client technology does not depend at all on the kind of service you will be talking to. Both WPF/Winforms and a Web app will be perfectly capable to talk to a web service.
Instead, choice of client technology should purely be driven by requirements on the client side
Factors that you should consider when coosing one client technology over the other are:
Know-How available to you (and your team)
Deployment scearios: How do you get your app to the users, etc.
Client environment: How many OSs do you need to support, how many different browsers would you have to support when doing a web app?
Do you have occasionally connected scenarios, or do you need privileged access to client resources? - This would tip the scale somewhat towards a Rich client.
Even so, in many cases a web app appears to be a very valid option as you have access to a wealth of non-MS tech like Javascript Frameworks, CSS resources etc. etc.
On a personal note: Do not use WCF to define your web services - there are fantastic Open Source Frameworks, most notably ServiceStack that will make you more productive and concentrate on what your service does and less on the mechanics and abstractions.
I can't find anything on the implementation of service discovery for the ASP.NET Web API. For a new project I need to make a decision between WCF and Web API. The service element will be consumed by a variety of clients, mobile, client-side JavaScript but also an ASP.NET website.
For the website the convenience of being able to generate a client against a WCF service is obviously a plus. I am not that familiar with RESTful web services but I see that there is Web Application Description Language (WADL). Maybe it is my ignorance but surely it is a good thing to be able to advertise the correct way to consume your service?
My main question: is there anything that generates a WADL or similar for WEB API?
Secondary question: this tool looks like it generates a client based on a WADL, is there anything else that makes life easy keeping a client up to date with a RESTful web service?
There is a considerable amount of work going in there. It is not finished but watch the space.
Having a look here (and newer Yao posts):
http://blogs.msdn.com/b/yaohuang1/archive/2012/05/21/asp-net-web-api-generating-a-web-api-help-page-using-apiexplorer.aspx
Also
http://blogs.msdn.com/b/yaohuang1/archive/2012/06/15/using-apiexplorer-to-export-api-information-to-postman-a-chrome-extension-for-testing-web-apis.aspx
I blogged an approach to generating WADL with ASP.NET Web API here: http://blogs.msdn.com/b/stuartleeks/archive/2014/05/20/teaching-asp-net-web-api-to-wadl.aspx
I am developing an application in asp.net mvc where i need to have Chat application intergrated in the web page. The chat application should be able to support group chat, private chat, simple file transfer and user should be able to create their own rooms.
Can u people tell me where i can buy a simple chat application with above functionalities. I need it immediately.
or
you could just suggest how to create my own application. The technology to use or just any idea to start.
As i said, i need this immediately, buying asp.net chat application with above functionalities is the best option.
and most important i should be able to integrate chat application in my existing MVC project. We are using ASP.NET MVC, Microsoft SQL Server 2005, Linq To Sql as database interaction tech and C#.
I wouldn't expect to find many commercial options for ASP.NET MVC based chat rooms, since platform is still quite young, plus most buyers would be able to use an "old fashioned" ASP.NET chat application (which is already widely available).
If you need something now, and you are willing to pay, I would say: buy an ASP.NET Forms chat and do a bit of plumbing to make it work against your user repository etc. I know of CuteChat, which is capable of doing this kind of integrating, but many components are likely to provide this feature.
Should you decide to build a chat application yourself - something that does not sound like a viable solution for something you need immediately - you might want to have a look at the AspComet library, which provides a service layer on top of ASP.NET to help you use COMET techniques (long polling etc).
If you need it "immediately" writing your own is pretty much out of the question. Creating a reliable chat service from the ground up takes time.
Pure ASP.Net (technically HTTP) chat services are highly unreliable. Even Facebook's and Google's HTTP chat clients despite their best efforts still have their issues. What you should be looking for is a Flash/Silverlight control of some kind.
If you're willing to forgo the file transfer capabilities there are a myriad of IRC clients that are capable of everything else you mentioned and IRC Servers range from cheap to free.
I am looking to create a lightweight, heavy traffic, db site. It will be standard 3 tiered architecture in asp.net. Part of this site is web-based, but most of the functions will ideally be available on mobile devices, also.
That being said, I know that web services is the classic answer for this, since I can access a web service from many platforms. However, I also know that ashx files are the most light-weight. Is there a way to access ashx files from non-web platforms? and if so, how would this compare to a web service to do the same thing.
a good example: a login page that calls either a web service or ashx file to authenticate.
Thanks!
Eric
[EDIT] I was thinking along the lines of iphone/android/pre type of mobile apps.
How will you display on the mobile devices? You've said "web-based" and "mobile devices" but these can be the same thing. E.g. Through Control Adapters
You should also look at ASP.Net MVC if you haven't. It should help with the tiered design and performance that you are looking to get out of your application.
An .ASHX file will efficiently deliver any content type that you require. That is one of it's key strengths. So the answer to your question is yes, it can be used to deliver to non-web platforms via SOAP or other HTTP transport schemes. This would be a lot more involved than using web services.
With your login example, then main benefit that I see is that your ASHX file can use multiple transport schemes, not just SOAP. So you can use the lighter weight REST for instance.
I have a need to explore VOIP integration into a .Net application. It would be incredibly helpful if the toolset was usable via ASP.Net (version 2.0 or higher), and provided the developer the option to allow interaction on the client either embedded within the web browser or external to the client web browser. It should be compatible at a minimum with Internet Explorer, but would be better if browser independence were an option.
I don't really understand your question -- what are you trying to DO with VoIP? Since you mentioned ASP.NET I'm guessing you mean some kind of server app? If you explain more about what you want to do, we can give you better advice.
You could check out Microsoft's Speech stuff: http://www.microsoft.com/speech/speech2007/default.mspx. As I understand it, Speech Server was moved into being part of OCS. I remember that it supported using .NET 3.0's Workflow Foundation as well as some multi-modal stuff with ASP.NET.
FreeSWITCH is a flexible VoIP system that works for both large-scale server implementations as well as embedded scenarios (say as an ActiveX softphone). There is full .NET and Mono support via mod_managed. (This allows you to create voice applications in FreeSWITCH using any .NET language.) There's also an XML-based API that allows you to send and receive events to control a remote FS server. You could use this from ASP.NET. FreeSWITCH is very active in #freeswitch#irc.freenode.net so you can get a lot of advice there.