As most developers know at this point, Parse is shutting down early 2017 but they have been pushing clients to migrate their services. I have a huge client who will be using Parse for Push Notifications in July and August and want to make sure that Parse will still be functioning 100%. I understand them wanting people to migrate, but they don't seem clear on whether their services will be interrupted.
They have been very clear about it :
Why are you using Parse when they are going to shut down & want you to adopt mongoDb? If you have an app there with mongo your app would work fine, but why not go with other options?
Refer : Parse Migration
Also read : My app relies on parse, I have no backend skills
Parse.com will be fully functional until the shutdown on January 28, 2017 although with weaker performance after April 28th.
According to members of the Parse team:
Hi there, I'm part of the team who is actively helping people migrate
their apps. The answer is that we don't know how this may affect push
notifications.
When we announced that the hosted Parse service will be shut down next
January, we also provided a migration guide where we have shared a
recommended set of guidelines for your migration:
Migrate your database by April 28th, 2016 Migrate your API traffic by
July 28th, 2016 We are committed to maintaining the Parse API up and
running until January of next year, but we highly recommend starting
your migration work as soon as possible. We are focusing our efforts
on people who are following our recommended instructions.
Source
and
If you have migrated your database to your own MongoDB, you will be
fine, your apps will receive full priority. If you haven't migrated
your database, you app will keep working, but requests might take
longer or have a higher failure rate.
Source
Related
When the "Duration" in https://developers.google.com/android/management/reference/rest/v1/enterprises.devices/issueCommand expires, no Time Out information comes from Pub/Sub. At the same time, when we query the command, there is no information that the command will no longer go. Can we perceive this?
Best regards.
This is not supported yet. Currently, Pub/Sub can display commands that are successfully submitted and commands that return errors.
There is an existing feature request for this but there is no guarantee when this will be worked on. To stay up to date with the latest updates for Android enterprise, we suggest that you join the Android Management API mailing list to receive monthly updates and service advisories directly to your inbox.
Do I need to change anything within my payment gateway script on my ecommerce website, so it complies with PSD2 requirements on sagepay hosted?
I don't take payments on my website, but redirect people to SagePay.
My question is according to Septembers EU law changes.
With any luck, you won't need to make any changes, as SagePay should handle the SCA process for you via 3D secure V2. You will probably already have needed to upgrade your protocol version from 2.x to 3.0 (https://www.sagepay.co.uk/support/12/36/sage-pay-version-3-00-understanding-the-process), and if you have, then SagePay should take care of the 3DS process for you, and hopefully will upgrade that process to 3DS2 when they see fit.
You will need to ensure that you have 3DS turned on in your SagePay account (https://www.sagepay.co.uk/support/28/36/activating-adding-a-3d-secure-rule)
This article:
https://www.sagepay.co.uk/support/12/36/3d-secure-explained suggests that "Depending on which payment integration your site uses with Sage Pay you may have to make some changes to the integration, so it is important to flag with your developer/IT that you may need to make some development changes in June / July / August to ensure they will be ready to act for you. Specific details will be available in May." However, it's now June, and I haven't seen any such "specific details".
I'm not involved with SagePay, so I don't have any further knowledge than that - we too have an integration with SagePay, so I'm also waiting for further confirmation from them on what steps will need to be taken.
EDIT January 2022
At some point between June 2019 and January 2022, SagePay, or rather Opayo, have indeed updated their integration and they do require changes in order to fully cater for 3DSv2. Specifically, you will need to upgrade from Version 3.00 of their integration to Version 4.00 and pass some additional data. The migration process is documented here
Essentially you need to send some additional SCA data and "Credential on File" (CoF) data if you intend to do repeat transactions.
If you use the SagePay REST API (I don't think this applies to OP) then there are some changes you may need to make, the docs for it are available at https://developer.sage.com/api/payments/api/
As far as I understand it the old system is still available and working but implementing these changes should allow you to use frictionless checkout (where 3DS is automatically confirmed) and 2FA.
while am trying to sign up to parse site, i cant able to find the option for sign up.
we have to implement parse push notification feature in xamarin mobile application development.
Please guide if any one have idea about registering to parse and the steps to work with push notifications too.
Unfortunately Parse (the service) is no longer available, its last day was Jan 30th 2017. Here's the first announce they made back in Jan 26 2016. They gave a whole year to every developer with hosting solution in Parse to be able to migrate it.
Parse became an open source project known as Parse-Server. You can use this but it will have to be as a self-hosted service.
If you don't feel like hosting Parse there are out there a few solutions that could get you running with for the Push Notifications. Just to name a few you have: Azure now known as Mobile Center, you have Firebase Cloud Messaging, Amazon SNS and a few others.
Since CodenameOne doesn't support "the cloud storage API" any more and the parse.com is going to retire soon as well. Does CodenameOne has any plan to release a new Cloud Storage API or provide suggestions/guidelines to help developers to deal with the parse4cn1 library code, cloud code, database structure and data in parse.com?
That is something you will have to figure out yourself as parse4cn1 was initially contributed by a community member and wasn't developed by Codenameone team.
You can use a simple webservices created in php, python or java, hosted along your content with any ISP.
You may also have a look at amazon aws which is promising, they provide a cloud solution but their SDKs is not yet integrated to Codenameone.
I made the parse4cn1 lib and I'm also wondering what's smartest to do. With the announcement of Parse.com's imminent shutdown, there's been a lot of discussion around alternatives. My feeling is that "the dust is yet to settle" as per what options are best and reliable for the longer term (it would be a pity to migrate to another service only for it to be shut down soon). So I personally plan to wait till sometime in Q2 to do a proper evaluation of the alternatives. Hopefully, there'll be more clarity then.
The option to host one's own Parse server (e.g. on AWS or Heroku) is getting interesting. They recently announced support for push notifications on iOS and Android. If (when?) they open source the Parse.com dashboard code, I think that option would be much more interesting.
At some point in the coming months, I plan to make a parse4cn1 release that exposes an option to set the server path. With that, anyone migrating to the Parse server option should, in principle, be able to continue to use the cn1lib. Of course, for features that are supported by the open source Parse server.
PS: Here are pointers to some of such discussions on Parse alternatives:
https://github.com/relatedcode/ParseAlternatives
http://www.slant.co/topics/5219/compare/~firebase_vs_kumulos_vs_kinvey
I have read about new Google Apps Marketplace and have seen the overview video here.
I'm worried about migration from OAuth1 to OAuth2 and having impact to some developed applications with APIs in my domaine
in the video exactely in 24', comparaison of what libraries/APIs are used in the OAuth1 vs OAuth2, and in 27' talking about turning off the OAuth1.
these Libraries/API will be deprecated ?
Any idea about turning off the OAuth1 and when ?
You need not worry about the impact of OAuth1 to OAuth2. This transition can be completed in a max of 15 days if you have done many integrations with Google. If you are worried just about the SSO with OAuth2 this can be completed in a day as Google has already provided proper documentation regarding the work flow.
Google has even provided migration APIs to upgrade your customers domains from v1 to v2 of Google Apps Marketplace(GAM). If you have a huge user base to be migrated then you need to plan accordingly such that migrated and non-migrated users would be able to use your app for some days till the migration is completed successfully.
Google will announce if it intends to discontinue or make backwards incompatible changes to this API or Service. Google will use commercially reasonable efforts to continue to operate those Google Documents List API versions and features identified at http://developers.google.com/google-apps/documents-list/documents-list-api-list without these changes until April 20, 2015, unless (as Google determines in its reasonable good faith judgment):
So on a safe side it is better to migrate all of your APIs to the latest libraries to avoid any failures at a later point of time. Anyway the older versions are not supported for any issue fixes/ support from Google side. So it is always better to migrate your APIs
Older version of GAM(v1) will also be deprecated at some time but Google hasn't provided any timeline for this. Probably it may take a year(not sure)
Google strongly encourages you to migrate your marketplace application to OAuth2 as soon as possible. Google has already announced deprecation of OAuth1. All top apps on marketplace have migrated their customers to OAuth2 with no issues. We plan to stop allowing installs of OAuth1 applications in near future from the marketplace (specific timelines to be communicated separately).