I am trying to get to know that how the Telegram API is working. I read the BOT API and i realized its based on HTTP requests.
I am wondering if the core API of telegram is the same, or not?
A simple explanation of how it's working would be a big help to me.
Telegram API offers a means of communicating securely with Telegram's Servers.
You may use either TCP, UDP or HTTP Transports.
To help you get started check out these few posts:
How to implement authorization using a Telegram API?
How to interact with Telegram API
Hope this helps.
Related
I have a WinForms application and I want to receive inbound SMS using Twilio. I am using VB.NET. The code that I find on the Twilio website are using web application and MVC. Can anyone help me how to use it in WinForms?
Did not get enough to try out anything.
Twilio uses a standard way of notifying your service, called webhooks. When an SMS, phone call, or something else happens, and you configure a webhook for that, Twilio will send HTTP requests to the URL configured as a webhook.
This does mean that you have to have a publicly running web server that can accept those HTTP requests with the details of the SMS, phone call, etc. That's why the samples will use ASP.NET, as this is only possible with web technology.
Winforms runs on your computer and doesn't expose any public web endpoints to receive the webhook HTTP requests, so you can't receive it directly. However, depending on your use-case, you have options.
If you don't need real-time updates, you can read the message history using the Twilio C# .NET SDK.
In your winforms app, you could add a button to refresh the messages on click. Alternatively, you could query the message X amount of seconds to give it a more real-time feel, even tho it's not really real-time.
Warning: to use the Twilio API to get the messages, you'll need to embed the Twilio credentials into your Winform app. Anyone that has access to your app will be able to read those credentials. Keep that security risk in mind!
The second option is to use ASP.NET to receive the webhook HTTP requests, and then use a SignalR or websockets to notify any connected clients, of which your winform app would be one.
For example, when Twilio receives an SMS, the ASP.NET application receives the webhook HTTP request, the ASP.NET app then send the SMS details to all clients connected to your SignalR hub, and then your Winforms app receives the SMS payload which you can use to render your app.
The second option is a lot more work and requires more infrastructure since the ASP.NET app needs to be hosted somewhere. We don't have a tutorial for that, but I'd be happy to forward more links to docs etc. if you have questions.
In order to implement the GCM on a app (developed by service.appinventor) I'm looking up a workaround to use HTTP REST API.
Unfortunately, by documentation https://developers.google.com/cloud-messaging/registration#automatic-retry-using-exponential-back-off
seems that I can only use Istance ID API.
Thanks
Has someone a suggestion?
I need a workaround to implement GCM registration (described here https://developers.google.com/instance-id/guides/android-implementation) using REST API.
Would it be possible to integrate the Uber APIs into a titanium app?
https://developer.uber.com/docs/tutorial-trip-experiences
Yes! You should be good to go! As long as you have a working HTTP protocol client that is able to make HTTP requests to the Uber API RESTful HTTP server and receive HTTP responses.
I am trying to make a sencha touch 2 mobile app. I have a restful api in server and i want to consume that in my mobile app. Which sencha proxy should i use (rest, ajax, jsonp)? Rest and ajax has issue with cross-site domain issue, so jsonp can be the solution. But how can i send jsonp request to rest api if i have parameters?
You can use REST proxy if your services truly follows REST standards because that way proxy can provide you out-of-the-box functionality to operate on models.
Regarding cross-domain issues, please note that the way app behaves in desktop browser is different from its behaviour when it runs in phone so you are not forced to use JSONP if you don't want, AJAX can also work for you. Its good if you can use JSONP but please keep in mind its limitations of having no support for HTTP headers and other useful methods like POST, PUT & DELETE.
Please go through this for more information : How to use json proxy to access remote services during development
I'm building a web application using GMails IMAP API. What would be the best way for me to make the updates "real-time"?
As of right now I'm using a Ruby Sinatra backend and backbone.js on the frontend. I'm looking for a way to make the communication between my frontend, my server, and the gmail api to be as fast and seamless as possible.
Thanks for the help
Edit: what I mean is what is the best way to make it seem real time. I realize gmail does not support web sockets. But what would be a good way of setting up my server and front end to make the data transaction as frictionless as possible.
I do not think this is possible. HTTP does not work this way. You would need WebSocket for this, but Gmail API does not support WebSocket.
You can either update info often (but you will run into google api request number limits).
Or update info when user needs it (that needs careful planning).