As I mentioned in my previous post, I’m doing a write up of our AJAX conventions and how they’re paying off for us.
In this series of posts, I’m going to cover a few topics:
I have not had time to make this code public yet, but I promise I’ll get around to it. In the meantime, I’ll explain the concepts and just gist the highlights.
I’ve released an initial v0.1 version of this called jQuery.continuations.
We start by hooking into jQuery’s global $.ajaxSetup call:
This is happening within a module block so the “self” is something I’ve declared above this piece of code.
Our convention is that unless you explicitly provide a success callback to any $.ajax call, you’re going to get this one for free.
I’ve talked about policies before and that’s exactly what we’re using to process the continuations. We have two functions: 1) matches(continuation) and 2) execute(continuation). Policies are registered via: $.continuations.applyPolicy() and we have several defaults.
Matches when refresh is true.
Simply refreshes the page.
Matches when url is not empty
Navigate the window to the specified url.
Matches when success is false and there are errors
Publishes the ‘ContinuationError’ topic through amplifyjs
Matches when the following properties exist: payload, topic
Publishes the specified topic and payload through amplifyjs
We have a couple more but I’ll save those for the next post.
The payloadPolicy is an interesting one. We knew that we were going to be working w/ websockets but we didn’t start with them. Instead, we used this infrastructure and simply shoved topics/payloads into our continuations. When a response was received, the information was published through amplify and we had structured our code to work against those topics.
When it came time to turn on websockets, we simply started publishing websocket messages through amplify and everything kept working like a charm.
Until next time.
Post Footer automatically generated by Add Post Footer Plugin for wordpress.