Skip to content
This repository was archived by the owner on Jan 4, 2023. It is now read-only.
This repository was archived by the owner on Jan 4, 2023. It is now read-only.

Networking Overview #9

@orta

Description

@orta
Contributor

This was discussed in an artsy hangout, but I wanted to get it into something actionable, Our NetworkingAPI should:

  • Make it easy to run offline
    Make it possible to run network requests synchronously
    Treat stubs as a first class citizen
    Allow tests to state only networking request X is allowed during this test run
    Allow iterating through all potential API requests at runtime for API sanity checks
    Keep track of current requests and don't support dupes

Think this is best done by having the request generation & the networking API client separate. A lot like how we have it in existing apps. Not assigning someone, but they should get ticked off as it happens, definitely better to do it earlier.

Activity

orta

orta commented on Aug 5, 2014

@orta
ContributorAuthor

I'd like the ability to easily cancel requests too, not really sure if that's the job of the PAI or the Network Models though.

orta

orta commented on Aug 6, 2014

@orta
ContributorAuthor

Ideally in this use case most of our requests should be cached, we could try having an API layer that insta-returns data synronously, then makes the network API call, updates the objects then does the async call. My gut impression is that this is how they do it in the tumblr app.

shepting

shepting commented on Aug 10, 2014

@shepting

Another great feature would be:

  • Don't emit a second network call, if a previous one for the same resource is already "in flight"
segiddins

segiddins commented on Aug 10, 2014

@segiddins
Contributor

@orta best bet might be to separate networking layer from your persistence layer and use something like NSFetchResultsController for that binding goodness

orta

orta commented on Aug 11, 2014

@orta
ContributorAuthor

I agree with both ( that's a smart one @shepting )

ashfurrow

ashfurrow commented on Aug 17, 2014

@ashfurrow
Contributor

(Working on something here)

orta

orta commented on Sep 3, 2014

@orta
ContributorAuthor

Closing, the responsibilities for this issue now lay in
screen shot 2014-09-01 at 10 51 36 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @shepting@orta@ashfurrow@segiddins

        Issue actions

          Networking Overview · Issue #9 · artsy/eidolon