Forgot your password?
typodupeerror

Comment: Re:The unseen enemy (Score 0) 510

by UnanimousCoward (#46016757) Attached to: Senator Dianne Feinstein: NSA Metadata Program Here To Stay

"We" voted for her because the alternative was...well...less savory. You can be sure that her support of NSA will be an issue the next time she comes up for re-election, and hopefully, a real Democrat challenger will emerge. But know this--if she withstands the challenge, "we" will be hard-pressed to vote for her Republican challenger...

Does that answer your rocks-glass-houses question?

Comment: Korean Aviation Culture (Score 1) 213

I have to admit that when I first heard about the crash, Gladwell's work came to my mind concerning Korean aviation culture. This train of thought was repeated over and over again on Twitter. This article talks about the past and present Korean aviation culture with respect to safety, and I think the writer is objective and reputable.

Comment: Re:is it even RESTful? (Score 1) 53

Yes, I realized the difference after taking a longer-than-quick look :-)

However, I still think there should be some notion of /object/{id} for GET. As per some of the other comments, I agree that what I'm talking about isn't a standard. I think it's more of a best practices implementation thing.

Comment: Re:is it even RESTful? (Score 1) 53

So I agree with just about everything you are saying here. I shouldn't have used the term "standard"--how about "best practices?" If ESRI or some other organization wants to put out a "RESTful API," then I think that it should adhere to some "best practices" which, IMHO includes the paradigm that I put forth (and is well-implemented in various web platforms).

Again, I agree with your stipulation that it is an IDEA or a CONCEPT (I've read the seminal thesis). But with respect to implementation, I think that there's another level that can be achieved.

Comment: is it even RESTful? (Score 3, Informative) 53

In taking a quick look a the standard, it doesn't even look RESTful. For example:

http://<mapservice-url>/layers

Returns deep copies of all layers and tables as opposed to a list of IDs. Then:

http://<featureservice-url>/<layerId>

Returns a deep copy of a particular layer/table.

How about http://<something>/layers returning a list of layers/tables and http://<something>/layers/{id} returning the particular table/layer? The whole /object and /object/{id} paradigm is missing. And that's just about GET. Regardless 800-lbs gorilla arguments against this "standard," I'd be more inclined to reject it due to its lack of adherence to standards.

Take care of the luxuries and the necessities will take care of themselves. -- Lazarus Long

Working...