Tag Info

Hot answers tagged

4

This is allowed by REST as long as your {key} URLs are discoverable; for example if doing GET /base-url/ returned a list of links to other valid REST resources, and among those were /base-url/{key} The main point is that out-of-band knowledge can't be required by a REST-conforming API; but if a provider publishes a specification the client is certainly ...


3

One benefit of http://webapp/api is that if you are developing the web site and the api as part of the same code base, you don't really need to do any special handling to deploy the api - it's just one web application that you have to deploy. If you did use api.webapp, for this case, then you would probably have to do some special handling during initial ...


3

Decoupling components from the database / getting away from direct database connections is a common pattern. Moving access into middleware / a component that front-ends the database can help improve security and modularity, and provide a place to implement data validation and interpretation that would otherwise "fall into" SQL, stored procedures, and ...


3

I think the overarching justification out of making data access a RESTful API would be the relationship the data access would have to the rest of the environment. Think about it, the power of the API is typically the vast amount and variety of "client" implementers that can consume it. That should be no different in your case. In other words, if you were ...


2

This is the preferred approach when you want multiple front ends to connect to the same server. Build a REST API and do not output any HTML or anything else other than JSON data. You can also have an authentication rest endpoint.


2

It's interesting to separate out system clocks, that provide the basic drumbeat for keeping gating circuits in synch with each other, and calendar clocks, that are used for tracking elapsed time over longer periods. The simplest form of calendar clock is driven off the alternating current power supply. This provides 60 cycles per second in the US, ...


1

Independent from implementing a key-value-store or whatever: you could use HATEOAS to describe your api. This enrichens the plain ressource information with meta-information what to do with your API. So in your example a call to base gives a collection of keys and their values: GET /baseurl/ gives you a resultset: [ { "links": { ...


1

Yes, adding a clock was complex for first computers, that's right. But some of the first computers simply WERE clocks. http://en.wikipedia.org/wiki/Antikythera_mechanism. What is interesting, the first universal computers were not afraid of clock using. ENIAC (1946) had a special cycling unit for synchronization of all its operations. It was not named ...


1

Many early time-sharing services would charge you by the millisecond for things like CPU time and memory time, and even dedicated data-processing systems (think company payroll and accounting systems) would have batch runs scheduled to run at certain times. I think large computer systems started having real-time clocks around the time they stopped being ...



Only top voted, non community-wiki answers of a minimum length are eligible