Anyone with more experience in JSON API, do you use included to proactively send resources? Why or why not? (CC @wycats @steveklabnik)
@Schoonology @steveklabnik because that means the instant you need when a tiny amount of more data you need a round trip
-
-
@wycats@steveklabnik Agreed, and I've been advocating this to clients. I also don't see anything in the spec to the contrary, but curious.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats@steveklabnik I've been advocating they consume (and cache) everything in "included", checking that cache for before desired GETs.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats@steveklabnik Hopefully that seems sane. Thanks again for codifying so much in the spec; client discussions are much easier! -
@Schoonology@wycats glad it's useful :) -
@steveklabnik@wycats I feel like you either use a spec like JSON API, or you wind up poorly engineering your own alternative over time.
-
@Schoonology@wycats literally why we made it. Glad to hear the messaging resonates :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.