5 ms·
I think the rules are different when you're creating an API that's supposed to be used by thousands of developers and millions of people right off the bat. FB
by swivelmaster 18y ago
I think the rules are different when you're creating an API that's supposed to be used by thousands of developers and millions of people right off the bat. FB is no longer a startup and developers are depending on them not just for the apps to 'work', but for their very livelihoods.
The app I'm working on for a living was brought down recently because FB changed the name of a method in their javascript library.
Once the origin of the bug was discovered it was easy to fix, but that's still a pretty unreasonable thing to do when, as was the case, a major library that is linked to from the very front of the wiki (the FB/AS3 bridge) is broken by an update.
It's also pretty painful when the median call to a certain specific API method is about a second or two, but the peak is literally ten seconds.
- almost 18y agoYou're depending on a facebook app for a living? How is that working? I thought after they moved apps to the Boxes Tab ghetto it would have pretty much killed off anything like that? Well done if it's working for you though, hope it continues to.
- albemuth 18y agoFacebook has a dev feed where they announce platform changes and they have a staging platform for you to test the new changes. And do not assume the api call is 2 seconds, now that you know this is not the case take measures(ajax) to minimize impact.
- swivelmaster 18y agoThey did not announce the change that I mentioned. In addition, the app broke on a Monday night, which is NOT when platform updates get rolled out. Someone was editing the code on the live site and made an undocumented change. The call I'm talking about is a javascript call made through a Flash app. The problem isn't that a page is timing out, the problem is that we have to wait for this call for the app to allow the user to continue.