Media Browser Integration

[UncleJohnsBand]

It's not a big difference sub's client key is a parameter called &md5= and sid is required too.

Martin

Ok... so it is just a parameter name thing..... then were ok....

[UncleJohnsBand]

I know, it's a GET. But to send some content, isn't it better to use a POST instead of the GET?
Or am i missing something in the REST methodology?

I'll change it to a post on the next build.... you still shouldn't be having a problem using the get.

[mvallevand]

Frankly I am getting fed up with all these unnecessary changes to the JSON interface.

Martin

[UncleJohnsBand]

Frankly I am getting fed up with all these unnecessary changes to the JSON interface.

Martin

I know..... but what Svekke pointed out is valid. Since this is a new API for NEWA and there are standards for REST based services I should be coding to the standard as much as possible.

[Svekke]

I know..... but what Svekke pointed out is valid. Since this is a new API for NEWA and there are standards for REST based services I should be coding to the standard as much as possible.

@Mvallevand: normally you only use a GET when you get some information.
You use a POST if you need to create something. Maybe this one is a tricky one. You "create" a session ....

[mvallevand]

It's not arbitrary data, the MD5 hash makes it url safe it's been working fine for sub an I can't imagine sub accepting a suggestion to change it to a POST. In fact earlier in this thread lukemb3 wanted you to change all your POSTs to GETs Its' not a big deal, I will just got back to using sub's call to login the sid is interchangeable.

Martin

[Svekke]

It's not arbitrary data, the MD5 hash makes it url safe it's been working fine for sub an I can't imagine sub accepting a suggestion to change it to a POST. In fact earlier in this thread lukemb3 wanted you to change all your POSTs to GETs Its' not a big deal, I will just got back to using sub's call to login the sid is interchangeable.

Martin

I will talk with Luke about that. Ot will be something for tomorrow. It's already late here.

[mvallevand]

@Mvallevand: normally you only use a GET when you get some information.
You use a POST if you need to create something. Maybe this one is a tricky one. You "create" a session ....

Using your logic the Instantiate should be a POST then.

Martin

[sub]

It's not arbitrary data, the MD5 hash makes it url safe it's been working fine for sub an I can't imagine sub accepting a suggestion to change it to a POST.

I wouldn't need to change anything. UJB is providing his own json interface to these, and calling my API classes directly. It doesn't change anything for me if his interface accetps GET or POST or accepts either.

[mvallevand]

Sub my point was your &md5= on the GET is not bad form just because someone thinks of it is data and you'd have need a better argument then was given to UJB before changing it.

Martin