A 12 billions market has been created just to address the need for bookkeeping
historic data, it's called business intelligence (BI).
Never heard of data warehouses and OLAP tools ? Many businesses use these
if they can pay for them
These things are cumbersome to implement, you have to
I just enjoy the speeches better by standing back a little bit.
Actually I'm quite annoyed that Rich doesn't say anything about how
important is to be able to forget facts, irreversibly filter things
out and reinvent the wheel again. Imagine a huge database full of
facts you're simply not
Rostislav Svoboda rostislav.svob...@gmail.com writes:
I just enjoy the speeches better by standing back a little bit.
Actually I'm quite annoyed that Rich doesn't say anything about how
important is to be able to forget facts, irreversibly filter things
out and reinvent the wheel again.
There are few -if any- concepts attached to REST; it is just a low-level,
ideologically-neutral technique. There is more than one way to do it,
hence you really can't talk 'against' it any more than you can talk against
hashmaps, for instance.
That said, getting RESTful design right is pretty
Rich was promoting functional programming. I can see functional programming
has its benefits, but you will need mutable states eventually somewhere to do
useful things. Functional programming just tell you to constraint yourself
when using mutable states. It's not like mutable states are to
Hi,
in my understanding, RESTful system design (as described in Roy Fielding's
dissertation) does not advocate hiding any state behind a bunch of
methods. :)
In REST, application state is carried by the representation that is passed
back and forth between the server and the client.
It seems to
i think per HTATEOAS, the methods are baked into the representations
that are transferred, as URLs. i mean, you gotta have methods
*somewhere* *somehow* that can *do stuff*, in an
application-context-sensitive manner.
--
You received this message because you are subscribed to the Google
Groups
Rich was promoting functional programming. I can see functional programming
has its benefits, but you will need mutable states eventually somewhere to
do useful things. Functional programming just tell you to constraint
yourself when using mutable states. It's not like mutable states are to be
It seems to me that a truly RESTful system design is very much in line
of what Rich was talking about.
This is completely correct. Let's take the common method GET for
instance. According to REST philosophy, GETs should be 100% cache-able (and
therefore they are actual values). We can disable
Hi Everyone... Quick question about Rich's latest talk:
In it he eloquently argues that you don't want to systems to communicate
with each other by calling each other's methods. Instead it is better to
just move values between systems that can also be queued.
It occurs to me that RESTful web
10 matches
Mail list logo
