I want to make an app that get push notification from server (iOS and android app). I'm interested in using Parse. I have heard in the past that parse push sometime delay up to 10 minutes or more. My app requires at most 2 minutes notification delay.
Can parse today do that job? or it still delay more than 2 minutes?
If it is delay more than 2 minutes what other solution you suggest me for push notification? I don't want difficult solution like making my own server or anything like that. I'm newbie please suggest me an easy solution.
I am using Parse for my app. Yes, I still experience delays, sometimes longer than a few minutes. But most of time, it feels instantaneous. I would suggest something more realtime if you really care about the response time (go check out pubhub etc.). If you stick to use push notifications, there is always a chance that you will get delay.
Related
I want to use Telegram Bot with enabled webHook,
Can I use Heroku free plan as my Bot's Url to hook up when received text message ?
I'm using Nodejs as language.
Yes, you can and it works fine. But Heroku will try to freeze your app for some time. In fact it can't be active for more than 18 of the last 24 hours.
And if you will prevent it, with ping your app or your bot will continuously receive messages, your app will recharge next 6 hours. It's a limit of the free plan.
I suggest that you use Openshift, it doesn't have such limits in free tier.
I guess another suggestion I can make is for you to use glitch.
I use glitch for all the bots I have made so far, it's free, easy to get started with. It also has the limitation where it sleeps after 5 minutes of your bot not being active.
In a post they say the reason why and how to solve it:
Apps sleeping is a large reason why we can offer the Glitch service
for free, so it’s not something we can turn off. However, we accept
that for some use-cases, like bots with no webhooks support, that’s
not ideal. It’s possible to expose a route in your app that a web cron
service or uptime monitoring service can hit and cause your bot to
wake. Doing that every 5 mins or so should do what you want.
Hope it helps.
I have a couple of telegram bots hosted on Heroku's free plan, with webhooks active.
They work fine but as mentioned in other answers the app is put to sleep after 30 minutes of inactivity: webhooks will reactivate it but when waking up there will be some lag and rarely some malfunctions (I lost a couple of commands).
There is a monthly limit of usage time but unless the bot is heavily used I found that this has not ever been a problem.
All in all I like the service, especially since it is free.
I have been testing some viewport issues for mobile and probably ran
git push heroku master
about 50 times in the last 3 hours. I am now seeing from the google speed tests that:
Reduce server response time In our test, your server responded in 8.9
seconds. There are many factors that can slow down your server
response time. Please read our recommendations to learn how you can
monitor and measure where your server is spending the most time. Hide
details
This wasn't popping up earlier this morning and was under .5 seconds. Did I damage one of my dynos on the heroku servers?= My site isn't really getting any traffic yet so I haven't been doing any stage testing.
What is the best way to test production?
I was reading through this but was wondering if there is a better way to test production quickly.
https://devcenter.heroku.com/articles/multiple-environments
Thanks,
Jeff
There's nothing wrong with pushing many times in a row, but every time you push, your dynos will cycle. This takes something like 5 to 15 seconds depending on the size of your slug.
Generally this means that the first query sent to your app at the moment your dynos are cycling might hang for about that long. If Google checked your server's speed at that time, then that explains the response time. However, there shouldn't be any lasting effects after you finish pushing repeatedly.
If I recall correctly there is a Heroku labs option to cycle dynos to eliminate this pause, basically taking down some of your dynos and then cycling them while the other ones are still up, but I do not recommend using it as it makes code pushes very unpredictable and can result in two versions of your app being live at the same time.
We're using herokus preboot lab to minimize downtime in our app, but it takes a few minutes for the new code to become live. Usually that doesn't matter, but sometimes we'd like to know when the new code is actually live to verify our fixes. Is there a way to tell if the new code is live besides just waiting for 10 minutes?
I am planning to write WP7 app, which needs to send to server phones GPS position every 5 minutes. Data must be sent to server even if app is not running. One way to do that is to use Background agents (I am using 7.5 Mango), but in that case app will send data only every 30 minutes, which is not acceptable in my case.
Is there any other solution?
Thanks in advice.
No, this is not a supported usecase for WP7 apps on Mango. Also, it's important to mention that the location you'll get for GeoCoordinateWatcher on a background agent is a cached geolocation from approximately the last 15 minutes and not the real-time geolocation.
What exactly are you trying to build if you don't mind me asking? This sounds oddly close to spyware. Even if it's innocuous and meant for a good purpose, I'd be careful walking in any direction that constantly shares GeoLoc with a remote server.
Your only choices are sending the data every 5 minutes while application is running (even when the phone is locked) and/or send the data once every 30 minutes by registering a PeriodicTask.
Having said that, I agree with Justin in that what you are describing sounds nefarious.
Ten updates a second, what would be the best way to do that? Aside from WebSockets (not fully implemented) what can accomplish this?
Would creating a Java Applet be worth it? Can you interact with the DOM in that fashion?
First 10 updates a second does not imply 10 messgaes a second to the browser, you can piggy-back updates to send one message a second (say) - no point in updates faster than the eye can see.
Commetd/Bayeuax worked for me.
Yes a JAVA Applet or any other Applet like Flex or Silverlight would be able to handle that speed.
As for the server side, I think you need a push server, you can't reach that rate of 10 responses / sec if each response is triggered by a client side polling request.
You you've got to let the flow of data come asynchronously from the server.
Examples of push server : Push Framework : http://www.pushframework.com