| Time |
S |
Nick |
Message |
| 00:02 |
|
|
fumanchu joined #rest |
| 00:05 |
|
|
fuzzyhorns joined #rest |
| 01:38 |
|
|
fumanchu joined #rest |
| 02:28 |
|
|
fuzzyhorns joined #rest |
| 02:32 |
|
|
baweaver joined #rest |
| 07:09 |
|
|
timg___ joined #rest |
| 07:12 |
|
|
timg___ joined #rest |
| 07:22 |
|
|
graste joined #rest |
| 07:30 |
|
|
timg___ joined #rest |
| 08:27 |
|
|
interop_madness joined #rest |
| 08:30 |
|
|
rosstuck joined #rest |
| 09:25 |
|
|
interop_madness joined #rest |
| 09:31 |
|
|
fumanchu_ joined #rest |
| 09:34 |
|
|
fumanchu joined #rest |
| 09:42 |
|
|
fumanchu_ joined #rest |
| 09:52 |
|
|
fumanchu joined #rest |
| 09:55 |
|
|
fumanchu joined #rest |
| 09:56 |
|
|
igitoor joined #rest |
| 10:00 |
|
|
igitoor joined #rest |
| 10:07 |
|
|
fumanchu joined #rest |
| 10:13 |
|
|
fumanchu_ joined #rest |
| 10:52 |
|
|
fumanchu joined #rest |
| 11:09 |
|
|
fumanchu_ joined #rest |
| 11:22 |
|
|
fumanchu joined #rest |
| 12:35 |
|
|
timg___ joined #rest |
| 12:58 |
|
|
timg___ joined #rest |
| 13:05 |
|
|
CentaurWarchief joined #rest |
| 13:41 |
|
|
metasansana joined #rest |
| 14:01 |
|
|
impl joined #rest |
| 14:03 |
|
|
znn joined #rest |
| 14:09 |
|
|
impl joined #rest |
| 14:13 |
|
|
xuxu joined #rest |
| 14:14 |
|
xuxu |
i would like to create a resource that has a name attribute, easy enough |
| 14:14 |
|
xuxu |
this resouce also needs another property that is essentially a mini program |
| 14:15 |
|
xuxu |
and the other is a table which for that mini program |
| 14:15 |
|
xuxu |
i have no clue how to make this restful |
| 14:15 |
|
asdf` |
what about this program? you mean you want to tell the server to run it? |
| 14:15 |
|
xuxu |
asdf`: yes |
| 14:15 |
|
xuxu |
it's more like a set of rules |
| 14:16 |
|
xuxu |
i guess that's more accurate than a mini-program |
| 14:16 |
|
asdf` |
sounds like you basically want a RPC service than a restful one |
| 14:18 |
|
|
impl joined #rest |
| 14:18 |
|
xuxu |
the server needs a set of rules and initial values, so that it may know how to operate on this asset later |
| 14:18 |
|
asdf` |
but i suppose yeah, you could have a /ruleset/123 resource, and a /tables/456 resource, and then have the client create a /analysis/abc resource with a {"ruleset":"/ruleset/123", "data":"/tables/456"}, and then the server would do the thing and update this resource with the results |
| 14:19 |
|
asdf` |
i don't think i have any more concrete ideas re. such a generic problem |
| 14:20 |
|
xuxu |
that was my initial guess |
| 14:20 |
|
xuxu |
but i don't know how to encode what is essentially a 2 column table in a post request |
| 14:20 |
|
asdf` |
oh, encode how? |
| 14:20 |
|
asdf` |
with json, a list of objects would work i think? |
| 14:22 |
|
xuxu |
i guess you can stringify json |
| 14:24 |
|
asdf` |
hmm, i don't think i understand the issue |
| 14:27 |
|
|
impl joined #rest |
| 14:31 |
|
xuxu |
i'm sorry asdf`, not trying to be mysterious over here. i'll write out what i think needs to be done, along with some code, and maybe that will clarify |
| 14:48 |
|
|
impl joined #rest |
| 15:00 |
|
|
impl joined #rest |
| 15:08 |
|
|
impl joined #rest |
| 15:14 |
|
|
foist joined #rest |
| 15:35 |
|
|
impl joined #rest |
| 15:53 |
|
|
impl joined #rest |
| 16:10 |
|
|
impl joined #rest |
| 17:12 |
|
|
wavded joined #rest |
| 17:17 |
|
|
_ollie joined #rest |
| 17:19 |
|
|
daxim joined #rest |
| 17:19 |
|
|
timg___ joined #rest |
| 18:54 |
|
|
nkoza joined #rest |
| 19:29 |
|
|
timg___ joined #rest |
| 20:30 |
|
|
spaceone joined #rest |
| 21:22 |
|
|
talios joined #rest |
| 23:52 |
|
|
fumanchu joined #rest |
