I have encountered Google's announcement for delay of termination date of GCM service, i knew it was originally 11, April 2019.
When GCM service stop date delayed?
As of April 10, 2018, Google has deprecated GCM. The GCM server and
client APIs are deprecated and will be removed as soon as May 29,
2019. Migrate GCM apps to Firebase Cloud Messaging (FCM), which inherits the reliable and scalable GCM infrastructure, plus many new
features. See the migration guide
Related
I am looking for a complete online reference for iManage's latest API. On googling, can see references to iManage v2 documentation, but that seems to be bit old and where can I find latest API if at all there is one
The latest version which is constantly updated is available at https://help.imanage.com/hc/en-us/sections/360000214214-iManage-Work-REST-API-Documentation - you'll need a login to IManage's support site to access this though. If you don't have credentials you can raise a ticket with your support provider to get access.
If you have an on premises server that's licenced for the API, you'll find the documentation for that specific version at https://YOURSERVERNAME/api-docs/
iManage has 3 different versions of API's
COM API > This is a legacy classic api which is reaching EOL on Dec 2023. So it is not recommended any more.
REST API v1.0 > EOL already reached (Dec 2022)
If you're on-prem technically you can use REST API 1.0 till iManage Work 10.4.4 (but please validate) but you will not have any support from iManage in case of any issues
REST API 2.0 (also called iManage Universal API)
This is the latest version and going forward you need to use this version. And if I am not wrong this is supported from iManage Work 10.2.3.
You can find latest documentation at iManage Universal API 2.0
Or you can find your Work server specific documentation https://YOURSERVERNAME/api-docs/ (Provided you entered API license while installing iManage Work software)
I have searched for the Whatsapp Business API but not found the official Whatsapp business API samples. What are the limitations of media messages and billing. If any one have information please provide.
The WhatsApp Business API Client supports a subset of the features provided by the WhatsApp applications you already know from Android, iOS, Web and other platforms including end-to-end encryption. The difference is that this application can be deployed on a server, providing a local API that allows you to programmatically send and receive messages and integrate this workflow with your own systems (CRMs, customer care, etc.).
You can check the media functionalities here. Also, you can start with the official doc.
We are currently using Stormpath for authentication. Our web application seems to be using a combination of Stormpath SDK calls and some REST calls.
I am aware that the Stormpath SDK will be shutting down August 17, 2017.
I'm trying to get my head around how we are going to migrate our code to Okta or even if we should. Should I just plan on rewriting the authentication portion of our application from the ground up? Stormpath says that Okta has not rewritten the SDK but will have REST apis that we can use temporarily. That sounds somewhat flaky.
Are there alternatives to Okta? My first priority is to find a service that is as stable as possible so that we don't have to migrate again anytime soon.
I have installed PushSharp for a while on our server and since GCM is deprecated, I wanted to know if somebody has already implemented Google Play Services with this package and what has to be done in the PushSharp code to support Google Play Services.
I'm looking for the client side and server side API for Lync 2010. But I found many API that can be able to develop. Anyone what are difference between all of them? Please help
Microsoft Lync Server 2010 SDK http://www.microsoft.com/downloads/en/details.aspx?FamilyID=58ccf6fd-31db-4f15-bafb-c5ef28afc5fc
Microsoft Unified Communications Managed API 3.0 Software Development
Kit
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=4493BAAB-6214-4770-8CF9-69C813E8A9FA
Microsoft Unified Communications Client API SDK
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=82c468da-3294-4ca9-bbcc-d455cfd06af2
Lync 2010 SDK is the latest Client-side SDK for Lync 2010 (doesn't work against previous versions). Its a fully managed (i.e. .Net) API, and allows you to build apps that automate the running instance of Lync to perform tasks, e.g. display presence and start a conversation from your LoB app (Automation mode). It also allows you to build your own custom clients to completely replace the Lync UI (UI Supression mode).
Unified Communications Managed API 3.0 (UCMA) is the latest server-side SDK for Lync 2010 (doesn't work against previous versions) - its also a fully managed API, and allows you to build applications that register to Lync as endpoints. This is useful for building bots, for example, a stock ticker bot that IMs people when a stock price goes over a certain threshold. You can also build call routing and IVR (interactive voice response) apps with this, and it can use Windows Workflow Foundation to reduce the amount of code you have to write.
Lync Server 2010 SDK is another server-side SDK, but rather than creating endpoints as per UCMA, this allows you to write filters that plug in to a Front End server. A filter allows you to inspect SIP traffic as it passes through the server, so its useful for building e.g. archiving solutions.
Unified Communications Client API (UCCA) is a client side API that allows you to build custom endpoints - e.g. Lync client replacements. This is best avoided, as it is COM based, so you have a lot more code to write, and need to be very careful about memory leaks. Its recommended to use Lync SDK in UI Supression mode, instead of this API. One benefit it does have though, is it works against Communicator 2007, Communicator 2007 R2 and Lync.
If you're developing against Lync and no previous versions, then Lync SDK (client) and UCMA 3.0 (server) should give you what you need. Otherwise, this article here talks about the previous SDKs in a bit more detail
Edit: I've expanded on this in a blog post
The main difference for me between Unified Communications Client API and UCMA was that UCC supports digest auth and that's why it is possible to build sip/rtp client for linux based asterisk.