Zotonic
Zotonic
zotonic@conference.zotonic.com
Monday, 10 June 2013< ^ >
Arjan has set the subject to: Zotonic - The Erlang Web Framework & CMS
Room Configuration

GMT+2
[01:26:40] mawuli.ypa leaves the room
[01:27:59] mawuli.ypa joins the room
[02:02:25] mawuli.ypa leaves the room
[02:02:38] mawuli.ypa joins the room
[06:29:56] bronzeboyvn joins the room
[09:34:16] Maas joins the room
[09:34:42] <Maas> Hey maximonster tribute on google. How did you manage to do that?
[09:39:29] Arjan joins the room
[10:03:21] <Maas> Hey Arjan, a client is reports a problem with comet on samsung devices. Do you know about an issue specific for samsung, as all the other android flavours we tested don't have this problem.
[10:12:33] <Maas> Btw, after reading the rules on the benchmark rules. Does "Use of an in-memory cache of Fortune objects or rows by the application is not permitted." mean that caching is allowed in the framework?
[10:12:46] <Maas> not application.
[10:31:02] <Maas> Oh, and erlang:now will uses a global lock. if you have lots of parallel calls it is better to use os:timestamp which is lockfree.
[10:47:09] Arjan leaves the room
[10:59:08] Arjan joins the room
[11:16:40] mawuli.ypa leaves the room
[11:30:50] mawuli.ypa joins the room
[12:52:03] mawuli.ypa leaves the room
[12:59:59] Arjan leaves the room
[13:39:15] Arjan joins the room
[13:42:09] bronzeboyvn leaves the room
[13:50:20] <Maas> Bought samsung tablet to fix this. Fun thing, "WebSocket" in window => true, but something is wonky after this. Does samsung support websockets? Weird I thought none of the android devices supported them.
[13:52:00] <Arjan> Maas: which android version?
[13:54:27] <Maas> 4.1.1 it looks like samsung devices support websockets somehow they don't switch to the fallback mechanism
[13:55:08] <Maas> the websocket api is there, but does not work, but also doesn't error.
[13:56:05] <Maas> This is also a problem on earlier android versions of samsung. Tested it in the shop on a couple of other devices.
[13:56:15] <Maas> Nice one.
[13:56:54] <Arjan> :(
[13:57:01] <Arjan> that is strange
[13:57:46] <Arjan> http://stackoverflow.com/questions/13349305/web-sockets-on-samsung-galaxy-s3-android-browser ?
[13:57:52] <Arjan> niks kunnen vinden op google?
[13:58:13] <Maas> Of course :-) stackoverflow... http://stackoverflow.com/questions/13349305/web-sockets-on-samsung-galaxy-s3-android-browser
[14:00:12] <Maas> Somehow the comet fallback was not triggered. Puts on hacking cap.
[14:07:50] <Maas> On a samsung device you can create a websocket object, but it is totally dead. None of the attached callbacks are called. Weird.
[14:10:07] <Maas> That's why it doesn't use the comet fallback mechanism.
[14:12:15] <Arjan> so it seems to work, but it doesn't.
[14:12:26] <Arjan> did you also check with different websites?
[14:12:33] <Arjan> e.g. different server implementations
[14:13:19] <Arjan> for instance this one, http://www.websocket.org/echo.html
[14:13:19] <Maas> No, not yet. Adding some debug prints to the handshake now.
[14:14:01] <Maas> Nice one. testing it right now.
[14:15:34] <Maas> It says "this browser supports websockets" but it never connects.
[14:15:42] <Maas> No errors.
[14:16:03] <Arjan> weird
[14:16:30] <Maas> Only on samsung.
[14:17:53] Arjan leaves the room
[14:19:40] <Maas> Comet fallback works of course, it only doesn't switch to it because everything seems ok. The ws.readyState is set to CONNECTING, but it never changes. Going to add a a timeout which checks the ready state so I can trigger the error callback when it times out.
[14:22:38] Arjan joins the room
[14:23:31] <Maas> Sigh, stupid, also a gap in the api spec btw, having no timeout on a connect.
[14:25:54] <Arjan> Maas: good solution
[14:26:02] <Arjan> how long for connect timeout?
[14:26:04] <Arjan> 10 seconds?
[14:26:09] <Arjan> or less?
[14:27:20] <Maas> Don't know what is a normal time here. It should not switch perfectly fine ws implementations to comet.
[14:27:35] <Maas> Some experimentation....
[14:28:45] Arjan leaves the room
[14:29:14] Arjan joins the room
[14:31:26] <Maas> It doesn't even try to connect, so no protocol problem
[14:32:39] Arjan leaves the room
[14:33:36] Arjan joins the room
[14:39:02] Arjan leaves the room
[14:42:40] Arjan joins the room
[14:57:50] <Arjan> argh
[14:57:57] <Arjan> they start drilling in the house next to me
[15:21:20] mawuli.ypa joins the room
[15:49:30] Arjan leaves the room
[15:49:54] Arjan joins the room
[15:50:51] mawuli.ypa leaves the room
[17:51:43] Maas leaves the room
[18:42:24] mawuli.ypa joins the room
[18:44:54] mawuli.ypa leaves the room
[18:49:43] mawuli.ypa joins the room
[19:02:13] Arjan leaves the room
[19:07:19] mawuli.ypa leaves the room
[19:36:18] Arjan joins the room
[20:18:27] <Arjan> mod_base_site's search.tpl searches on mailinglist categories
[20:18:34] <Arjan> that causes a warning in the system
[20:18:44] <Arjan> 20:07:39.081 [warning] Query: unknown category mailinglist
[21:07:22] <Marc Worrell> and when you install mod_mailinglist? :)
[21:16:53] <Arjan> :P
[21:17:13] <Arjan> mod_base_site should have a dependency on mod_mailinglist, is what Im saying
[21:18:03] <Marc Worrell> I am not sure - because I would like to run mod_base_site without mod_mailinglist
[21:18:25] <Marc Worrell> but if mod_mailinglist is running then I would like to see mailinglists in my search results...
[21:19:38] <Arjan> then the search should maybe be more generic?
[21:19:54] <Marc Worrell> yep - but how???
[21:19:57] <Arjan> or make mailinglist a subcategory of collection or something
[21:20:10] <Marc Worrell> or make the search a stored search query?
[21:20:20] <Arjan> also nice
[21:20:51] <Marc Worrell> then you can add&remove categories - without changing the templates
[22:55:44] Andreas Stenius leaves the room
[23:23:30] Maas joins the room
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!