Time |
S |
Nick |
Message |
00:15 |
|
|
talios joined #rest |
00:19 |
|
|
m0ltar joined #rest |
01:02 |
|
|
talios joined #rest |
01:08 |
|
|
talios joined #rest |
02:49 |
|
|
daxim joined #rest |
03:14 |
|
|
daxim joined #rest |
03:21 |
|
|
DrCode joined #rest |
03:44 |
|
|
wilmoore joined #rest |
05:22 |
|
|
adaro joined #rest |
06:14 |
|
|
adaro joined #rest |
06:41 |
|
|
adaro joined #rest |
07:02 |
|
|
graste joined #rest |
07:15 |
|
|
ph88_ joined #rest |
07:23 |
|
|
_ollie joined #rest |
07:48 |
|
|
rosstuck joined #rest |
07:55 |
|
|
wilmoore joined #rest |
08:22 |
|
|
ssedano joined #rest |
09:22 |
|
tmoore |
chovy: why do you think that's cumbersome? That sounds like it makes a lot of sense to me. |
09:22 |
|
tmoore |
Although... if jobid is unique, you could really just use /api/jobs/:jobid |
09:24 |
|
tmoore |
That would work whether or not you're an admin... you'd just do the permission check in whatever handles that URL |
09:25 |
|
tmoore |
Actually, I'm assuming that you're wanting to delete the whole job, not just remove it from the list of favorites |
10:07 |
|
|
shrink0r joined #rest |
10:28 |
|
|
DrCode joined #rest |
10:44 |
|
|
DrCode joined #rest |
12:17 |
|
|
danizord joined #rest |
13:41 |
|
|
saml joined #rest |
13:51 |
|
|
charlie joined #rest |
14:03 |
|
charlex |
howdy people, quick question |
14:04 |
|
charlex |
let's say I have this endpoints /photos, /tags, /galleries and I can LINK a /photos/{id} to a /galleries/{id} and also can LINK a /photos/{id} to a /tags/{tag}, everything's fine till there |
14:04 |
|
charlex |
but I'm having issues to design an endpoint in where I can search (GET) the /photos linked to a specific /galleries/{id} and a specific /tags/{tag} |
14:04 |
|
charlex |
thoughts? |
14:19 |
|
|
_ollie joined #rest |
14:20 |
|
|
Left_Turn joined #rest |
15:06 |
|
|
ph88_ joined #rest |
15:45 |
|
|
wilmoore joined #rest |
15:58 |
|
|
_ollie1 joined #rest |
17:06 |
|
|
graste1 joined #rest |
18:17 |
|
|
_ollie joined #rest |
18:52 |
|
|
m0ltar joined #rest |
19:26 |
|
|
DrCode joined #rest |
19:26 |
|
|
_ollie joined #rest |
19:35 |
|
|
shrink0r joined #rest |
20:05 |
|
|
MadLamb joined #rest |
20:16 |
|
|
wilmoore joined #rest |
20:20 |
|
MadLamb |
Hey guys, do any1 know if its ok to return a structure different from the one being send in a post (create) in HAL? |
21:06 |
|
whartung |
you can return whatever you want MadLamb |
21:10 |
|
|
m0ltar joined #rest |
21:11 |
|
MadLamb |
whartung, yes i can, but isnt there a recommended way? |
21:11 |
|
MadLamb |
whartung, this service i'm writing will not have any persistence. |
21:12 |
|
MadLamb |
whartung, its a shipment quote, |
21:50 |
|
|
DrCode joined #rest |
22:00 |
|
|
talios joined #rest |
22:04 |
|
whartung |
MadLamb: it should have some persistence. What should happen is you POST should result in a REDIRECT to the actual /quote resource. They should be able to retirve that quote for at least as long as the quote is good for |
22:06 |
|
MadLamb |
whartung, from the moment the response is sent, the quote will be considered invalid. |
22:06 |
|
talios |
Morning |
22:07 |
|
whartung |
well, logically, that doesn't make much sense. of what use is an invalid quote (yes I'm being pedantic here, but computers tend to be pedantic). Operationally, from a resource perspective, persisting the quote for the duration of the TTL of the quote is useful and valuable, whether the quote is good for 10s or 6 months. |
22:20 |
|
MadLamb |
whartung, dont that mean unnecessary load for the server? database/cache access? |
22:22 |
|
whartung |
it's a static document. How much load can that be? And it's completely cacheable. You can even set the cache limite to the TTL of the quote. |
22:22 |
|
whartung |
do you database processing, write the result to a file, reply with a redirect to that file, and you're done. |
22:22 |
|
whartung |
then write a clean up process to purge old quotes |
22:22 |
|
whartung |
simple, low impact, RESTful |
22:23 |
|
MadLamb |
whartung, this service returns many carrier services, it has to update the quote with those carriers, and they don't guarantee the price for a specific time range, so how could I? Everything depends on weight |
22:24 |
|
MadLamb |
whartung, every single request returns a different result. |
22:25 |
|
whartung |
so if I get a quote from you it's not going to be honored? |
22:25 |
|
MadLamb |
whartung, its the only service with that behavior in the api. |
22:25 |
|
MadLamb |
whartung, no. |
22:25 |
|
whartung |
so, this is an "estimate", not a quote? |
22:25 |
|
MadLamb |
whartung, yes. |
22:25 |
|
MadLamb |
whartung, it will be honored on the moment you place the order. |
22:25 |
|
whartung |
how long do I have to place the order |
22:25 |
|
whartung |
? |
22:25 |
|
MadLamb |
whartung, but you can get the quote now and place the order in 3 days. |
22:26 |
|
whartung |
and how do you know what estimate I'm basing my order upon? |
22:26 |
|
MadLamb |
whartung, or even more. |
22:26 |
|
whartung |
so it DOES have a life span |
22:26 |
|
MadLamb |
whartung, actually you dont provide the quote id, but the service you want it to be delivered. |
22:27 |
|
MadLamb |
whartung, the price may be different at that time. |
22:27 |
|
whartung |
so how do I know if you're honoring your quote? Do I just tell you how much I want to pay, based on what you told me? |
22:27 |
|
whartung |
so, it's not a quote. it's an estimate. |
22:27 |
|
whartung |
a good faith estimate, but still an estimate |
22:27 |
|
MadLamb |
whartung, you can get the quote now, and place the order in tree years, certainly the price is different and you'll have to pay the new one. |
22:27 |
|
MadLamb |
whartung, yes, its an estimate |
22:28 |
|
whartung |
so that's my point, you will not honor the quote, it's a "good faith estimate subject to change without notice" |
22:28 |
|
MadLamb |
whartung, yes. |
22:29 |
|
MadLamb |
whartung, you're right, but that means i dont need persistence, right? |
22:29 |
|
whartung |
Well, for one thing, I'd change the name of it. "quote" means something. |
22:29 |
|
MadLamb |
whartung, ill do that. |
22:29 |
|
whartung |
no, you can make it a simple service. |
22:32 |
|
MadLamb |
whartung, thanks :) |
22:33 |
|
whartung |
yw |
23:53 |
|
|
Left_Turn joined #rest |