Time |
S |
Nick |
Message |
00:22 |
|
|
quimrsto_ joined #rest |
00:23 |
|
|
Guest28277 joined #rest |
01:32 |
|
|
jgornick joined #rest |
02:11 |
|
|
tbsf joined #rest |
02:30 |
|
|
tbsf joined #rest |
06:30 |
|
|
tbsf joined #rest |
07:52 |
|
|
interop_madness joined #rest |
08:06 |
|
|
Haudegen joined #rest |
10:31 |
|
|
tbsf joined #rest |
10:34 |
|
|
vanHoesel joined #rest |
11:31 |
|
|
vanHoesel joined #rest |
12:02 |
|
mac- |
hmm |
12:02 |
|
mac- |
there are media types that are not text based |
12:03 |
|
mac- |
in such cases, it's also possible to include hypermedia controls as a part of the representation metadata |
12:03 |
|
mac- |
right? |
12:04 |
|
mac- |
but now is my question: how hypermedia controls can be part of representation metadata, when representatoion metadata is a HTML head? |
12:04 |
|
asdf |
it's not really hypermedia, if the controls are in the metadata, is it? |
12:04 |
|
mac- |
and hypermedia controls are part of HTML body ? |
12:04 |
|
asdf |
the non-text-based thing wouldn't be hypermedia, i mean |
12:05 |
|
mac- |
as I understand it can be i.e. image/photo |
12:05 |
|
mac- |
its binary |
12:05 |
|
mac- |
not text |
12:05 |
|
asdf |
right |
12:05 |
|
asdf |
there's the Link header, but i'm not sure there's much more than that |
12:05 |
|
mac- |
uhm |
12:06 |
|
mac- |
then you will have in header: Accept: image/png Link: www.sth.com/photos/photo.png |
12:06 |
|
mac- |
? |
12:07 |
|
asdf |
it's a response header really... i guess Link: http://blabla.jpg; rel=next_image |
12:08 |
|
mac- |
but rel is not part of header ? |
12:09 |
|
asdf |
but uh, i suppose it's fine to just have your images be images, not really part of your api? have resources that link to a jpg file and have all the required relations there - /images/123 returns an actual json object that has all the relations etc, but also a link to a static http://.com/blabla.jpg image |
12:09 |
|
asdf |
rel is part of the header in this example |
12:10 |
|
|
Haudegen joined #rest |
12:11 |
|
mac- |
yeah, the resource that map[s to image |
12:11 |
|
mac- |
not direct image |
12:21 |
|
mac- |
by 'not really part of your api' you mean that I use image contents as several hypermedia controls ? |
12:22 |
|
mac- |
it is really abstract but I would get images which shows sth and try to use areas of image as hypermedia conrteols ? |
12:23 |
|
asdf |
i mean that the resource contains just a link to the actual image file, and the actual image files are external to it; as you put it, you only have resources that map to images; the actual image files are on a non-restful fileserver, s3, or something |
12:23 |
|
mac- |
yep |
12:23 |
|
asdf |
the resource that contains the link to the actual image can of course be regular hypermedia, no need to use metadata |
12:24 |
|
asdf |
i guess there are image formats that are hypermedia... svg? |
12:24 |
|
mac- |
I really don;t know much about different kind of graphics techjnology ;p |
12:24 |
|
mac- |
technologies |
12:25 |
|
mac- |
but graphics file is one of possible representations of a resource |
12:59 |
|
mac- |
but |
12:59 |
|
mac- |
but |
13:01 |
|
mac- |
by 'there are media types that are not text based' we should understand sth which will replace HTML to not-text based medium? |
13:02 |
|
mac- |
hm nope it means that HTML will carry non-text content |
13:03 |
|
mac- |
inside which hypermedia controls will be delivered |
14:13 |
|
|
foist_ joined #rest |
15:26 |
|
|
tbsf joined #rest |
16:39 |
|
|
wsieroci joined #rest |
17:04 |
|
|
Guest35960 joined #rest |
17:07 |
|
|
tbsf_ joined #rest |
17:29 |
|
|
Haudegen_ joined #rest |
17:55 |
|
|
tbsf joined #rest |
18:04 |
|
|
tbsf joined #rest |
18:18 |
|
|
tbsf joined #rest |
18:30 |
|
|
tbsf joined #rest |
19:38 |
|
|
wsieroci joined #rest |
19:52 |
|
|
Haudegen joined #rest |
20:09 |
|
|
tbsf joined #rest |
21:45 |
|
|
Haudegen_ joined #rest |
22:02 |
|
|
Haudegen joined #rest |
22:35 |
|
|
Haudegen joined #rest |
23:10 |
|
|
Haudegen joined #rest |