| Time |
S |
Nick |
Message |
| 00:30 |
|
|
shrink0r_ joined #rest |
| 00:33 |
|
|
begriffs joined #rest |
| 00:44 |
|
|
arbelos joined #rest |
| 01:08 |
|
|
shrink0r joined #rest |
| 01:14 |
|
|
shrink0r_ joined #rest |
| 01:17 |
|
|
shrink0r joined #rest |
| 01:20 |
|
|
shrink0r_ joined #rest |
| 01:57 |
|
|
shrink0r joined #rest |
| 03:00 |
|
|
lemur joined #rest |
| 03:54 |
|
|
LemonUK left #rest |
| 03:57 |
|
|
ewalti_ joined #rest |
| 04:45 |
|
|
fumanchu joined #rest |
| 04:52 |
|
|
ewalti joined #rest |
| 06:09 |
|
|
fsvehla joined #rest |
| 07:11 |
|
|
interop_madness joined #rest |
| 07:31 |
|
|
fumanchu_ joined #rest |
| 07:36 |
|
|
graste joined #rest |
| 07:54 |
|
|
quimrstorres joined #rest |
| 08:02 |
|
|
quimrstorres joined #rest |
| 08:11 |
|
|
Left_Turn joined #rest |
| 08:11 |
|
|
quimrstorres joined #rest |
| 08:14 |
|
|
quimrstorres joined #rest |
| 08:18 |
|
|
quimrsto_ joined #rest |
| 08:21 |
|
|
shrink0r joined #rest |
| 08:27 |
|
|
quimrstorres joined #rest |
| 08:33 |
|
|
fumanchu joined #rest |
| 08:45 |
|
|
Andre-B joined #rest |
| 08:48 |
|
|
ewalti joined #rest |
| 08:49 |
|
|
ewalti joined #rest |
| 09:57 |
|
|
mezod joined #rest |
| 10:24 |
|
|
ewalti joined #rest |
| 10:52 |
|
|
Andre-B_ joined #rest |
| 11:47 |
|
|
eschmidbauer joined #rest |
| 12:30 |
|
|
ewalti joined #rest |
| 13:25 |
|
|
dkm joined #rest |
| 13:28 |
|
|
quimrstorres joined #rest |
| 14:11 |
|
|
saml joined #rest |
| 14:39 |
|
|
ewalti joined #rest |
| 15:33 |
|
|
saml joined #rest |
| 16:00 |
|
|
ewalti joined #rest |
| 16:18 |
|
|
ewalti joined #rest |
| 16:29 |
|
|
mlpppp_23 joined #rest |
| 16:31 |
|
mlpppp_23 |
sever-side session are not REST, right? so if I need to make my REST resource accessible to different user groups with different rights, how would i go about that? because if i let the user get a token via myAPI/getToken/, i would have to save the token somewhere in the DB to identifiy the user.. would that still be RESTful? Thx! |
| 16:35 |
|
whartung |
typicaly you have them authenticate each time mlpppp_23 |
| 16:35 |
|
pdurbin |
mlpppp_23: we save our users' API tokens in our database. gotta put them somewhere |
| 16:48 |
|
|
ewalti joined #rest |
| 16:52 |
|
|
benaiah joined #rest |
| 16:57 |
|
|
benaiah joined #rest |
| 16:59 |
|
|
jenia joined #rest |
| 17:00 |
|
jenia |
hello. do browsers use the ERST protocol for communication? |
| 17:01 |
|
asdf` |
jenia, browsers mainly use HTTP, and some others sometimes too |
| 17:01 |
|
asdf` |
REST isn't a protocol, it's a, uh, architectural style |
| 17:01 |
|
asdf` |
or, an idea about how to write programs |
| 17:02 |
|
whartung |
Browsers are also terrible REST clients... |
| 17:10 |
|
mlpppp_23 |
pdurbin, so each time, when the user logs in, you generate a token for him? |
| 17:11 |
|
|
Andre-B joined #rest |
| 17:12 |
|
pdurbin |
no. that sounds more like a session cookie |
| 17:12 |
|
pdurbin |
ours are like GitHub's. you create a token for yourself and start using it. it doesn't change |
| 17:12 |
|
mlpppp_23 |
pdurbin, and where does the user store the token? |
| 17:14 |
|
pdurbin |
mlpppp_23: when this is done it'll be stored in their Android app data cache thingy: https://github.com/IQSS/dataverse-android/issues/1 |
| 17:14 |
|
pdurbin |
per server |
| 17:14 |
|
pdurbin |
since the app supports connecting to multiple servers |
| 17:15 |
|
mlpppp_23 |
pdurbin, i see. but if the client is an ordinary web browser where chanches are high the user clears the cache, how would you save the token? also, when it's a multi user enviroment, i.e. one physical client machine might be used by different users with different rights in the application. |
| 17:17 |
|
pdurbin |
with a normal web browser you don't need a token for our app. you just log in and you get a session, which is stored in a cookie with a jsessionid (standard java webapp stuff) |
| 17:18 |
|
mlpppp_23 |
pdurbin, yeha but that wouldn't be rest in the strict sense if i understood everything correctly. |
| 17:18 |
|
pdurbin |
right |
| 17:19 |
|
|
Lobosque joined #rest |
| 17:20 |
|
mlpppp_23 |
pdurbin, because i actually want to use Jersey.. i.e. i will use HttpServletRequest |
| 17:21 |
|
mlpppp_23 |
as with "normal" web applications |
| 17:21 |
|
|
tieTYT2 joined #rest |
| 17:21 |
|
pdurbin |
yeah, we use Jersey too |
| 17:22 |
|
mlpppp_23 |
http://sparkjava.com also looks interesting. |
| 17:22 |
|
pdurbin |
sure does |
| 17:23 |
|
mlpppp_23 |
How session data is handled in HttpServerRequest is determined by the web container, right? |
| 17:23 |
|
mlpppp_23 |
*i mean saved |
| 17:27 |
|
pdurbin |
mlpppp_23: saved where? I'm confused. |
| 17:28 |
|
mlpppp_23 |
pdurbin, where the session data is stored on the server-side, i.e. in files, in a RDBMS, in Memcached etc.. |
| 17:29 |
|
pdurbin |
hmm. good question |
| 17:30 |
|
pdurbin |
whartung: do you know where glassfish puts them? |
| 17:30 |
|
whartung |
sec... |
| 17:36 |
|
mlpppp_23 |
pdurbin, it depens on the configuration. |
| 17:40 |
|
pdurbin |
mlpppp_23: what's the default? |
| 17:41 |
|
mlpppp_23 |
mlpppp_23, that i don't know, but the web containers can usually configured how they save the data. say you have a high-traffic website, you probably need a session management that doesn't use flat files. |
| 17:41 |
|
whartung |
allright, what are we babbling about? |
| 17:41 |
|
mlpppp_23 |
mlpppp_23, but i am new to the java world myself.. |
| 17:41 |
|
mlpppp_23 |
lol pdurbin i mean |
| 17:41 |
|
mlpppp_23 |
was talking to my self by accident lol |
| 17:42 |
|
pdurbin |
whartung: when glassfish gives me a cookie where on the server is the jsessionid stored? in memory? on disk? |
| 17:42 |
|
whartung |
in memory |
| 17:42 |
|
pdurbin |
ok. thanks |
| 17:42 |
|
whartung |
it will persist to disk on shutdown |
| 17:42 |
|
pdurbin |
where on disk? |
| 17:43 |
|
mlpppp_23 |
whartung, would you say that in-memory store is okay if i only store two integer values (isLoggedIn UserID) per session even if I have up to 100 concurrent sessions? |
| 17:43 |
|
whartung |
I think Glassfish can find the 2K of RAM that will take and still be able to function realiably mlpppp_23 |
| 17:43 |
|
whartung |
I have no idea where, somewhere in the domain folder pdurbin |
| 17:44 |
|
mlpppp_23 |
whartung, so you would not worry about that? in my case it's tomcat, but it comes down to the same. |
| 17:45 |
|
mlpppp_23 |
mlpppp_23, i think i just used DB-stored session way to long and am therefore worried that i might run out of memory lol |
| 17:50 |
|
|
ewalti joined #rest |
| 17:55 |
|
whartung |
no I wouldn't worry about it |
| 17:56 |
|
whartung |
there are options for disk base session managers and such, I've never used them |
| 17:56 |
|
whartung |
we cluster glassfish, but we don't cluster web sessions |
| 17:59 |
|
mlpppp_23 |
i see |
| 17:59 |
|
whartung |
I should say, we load balance with glassfish, and ad hoc cluster -- we dont use native GF clustering |
| 18:00 |
|
whartung |
our JMS is clustered, however |
| 18:00 |
|
mlpppp_23 |
whartung, thx for the many info. |
| 18:00 |
|
whartung |
yw |
| 18:07 |
|
|
DrCode joined #rest |
| 18:49 |
|
|
quimrstorres joined #rest |
| 19:15 |
|
|
shrink0r joined #rest |
| 19:57 |
|
|
warehouse13 joined #rest |
| 20:08 |
|
|
tieTYT2 joined #rest |
| 21:24 |
|
|
quimrstorres joined #rest |
| 21:48 |
|
|
quimrstorres joined #rest |
| 21:54 |
|
|
quimrstorres joined #rest |
| 22:09 |
|
|
mezod joined #rest |
| 22:18 |
|
|
Andre-B_ joined #rest |
| 22:24 |
|
|
quimrstorres joined #rest |
| 23:06 |
|
|
shrink0r joined #rest |
| 23:30 |
|
|
eschmidbauer__ joined #rest |
| 23:31 |
|
|
fumanchu_ joined #rest |
| 23:35 |
|
|
trygvis_ joined #rest |
| 23:37 |
|
|
Jefffrey joined #rest |
| 23:38 |
|
|
pgicxplzs joined #rest |
| 23:38 |
|
|
daxim_ joined #rest |
| 23:39 |
|
|
asta22 joined #rest |
| 23:39 |
|
|
pgicxplzs joined #rest |
| 23:41 |
|
|
pgicxplzs joined #rest |
| 23:43 |
|
|
pgicxplzs joined #rest |
| 23:44 |
|
|
pgicxplzs joined #rest |
