“Middle ground” architecture for client-server iOS apps?
I see two obvious approaches to the architecture for an iOS app which needs to talk to a server to do its job.
What’s the best way of building an administrative UI for an existing SPA application?
I’m working on an application where the client-side interface and backend server are completely separate applications. The backend is written in Ruby and only serves JSON via HTTP. The client is a completely “static” single-page browser application that communicates with the JSON API. I now need to build an administrative interface that will be used to curate content served by the JSON API.
What’s the best way of building an administrative UI for an existing SPA application?
I’m working on an application where the client-side interface and backend server are completely separate applications. The backend is written in Ruby and only serves JSON via HTTP. The client is a completely “static” single-page browser application that communicates with the JSON API. I now need to build an administrative interface that will be used to curate content served by the JSON API.
What’s the best way of building an administrative UI for an existing SPA application?
I’m working on an application where the client-side interface and backend server are completely separate applications. The backend is written in Ruby and only serves JSON via HTTP. The client is a completely “static” single-page browser application that communicates with the JSON API. I now need to build an administrative interface that will be used to curate content served by the JSON API.
What’s the best way of building an administrative UI for an existing SPA application?
I’m working on an application where the client-side interface and backend server are completely separate applications. The backend is written in Ruby and only serves JSON via HTTP. The client is a completely “static” single-page browser application that communicates with the JSON API. I now need to build an administrative interface that will be used to curate content served by the JSON API.
What’s the best way of building an administrative UI for an existing SPA application?
I’m working on an application where the client-side interface and backend server are completely separate applications. The backend is written in Ruby and only serves JSON via HTTP. The client is a completely “static” single-page browser application that communicates with the JSON API. I now need to build an administrative interface that will be used to curate content served by the JSON API.
Is “friendly fire” session replay a valid concern?
I’ve been reading a lot about sessions and security, trying to learn as much as possible before writing too much code. I’ve read about limiting session replay by including a timestamp within the cookie or data sent by the server:
Is “friendly fire” session replay a valid concern?
I’ve been reading a lot about sessions and security, trying to learn as much as possible before writing too much code. I’ve read about limiting session replay by including a timestamp within the cookie or data sent by the server:
Mutual Authentication in JSON or AJAX only?
AFAIK we must install the client-certificate into the users browser to connect with https-sites using server-certificates to have a mutual authentication.
Bulk update in client-server application
Sometimes when coding a client-server application, the client needs to make a bulk update. For example: “mark all pending orders as dispatched”. To implement these I typically write specific controller methods, which perform the required database operation.