This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[00:25:39] * ChanServ sets mode: +o temporalfox [00:32:50] * ChanServ sets mode: +o temporalfox

[00:52:23] * ChanServ sets mode: +o temporalfox [01:28:30] * ChanServ sets mode: +o temporalfox

[08:56:00] * ChanServ sets mode: +o temporalfox [11:59:43] <qsys> If one implements his own messagecodec, which is a byte[], this byte[] is sent over websockets as well, I suppose? Is there any way to circumvent this? It would make sense to sent 'inside' an application other types than 'outside' to clients (for which json is more like a standard)? [12:00:29] <aesteve> you mean through eventbusbridge ? [12:00:48] <qsys> well, yeah :) [12:01:07] <aesteve> never tried but I'd be interested to know, actually [12:02:02] <qsys> as long as a message is 'behind' the bridge, it would be nice to have your own codec… Sending to clients, however, well, this might be rather unreadable in some cases. Unless you use json for everything, which is the understandable standard. [12:04:11] <qsys> having a 'decodeToEBBridge' and 'deocdeFromEBBridge' whould be useful, I suppose? Now, I use two different addresses. I just started wondering if that makes sense. [12:05:36] <aesteve> on the bridge options, why not [14:19:29] <BadApe> is there a way to automatically close a jdbc when you go out of scope? [16:25:48] <Sticky> BadApe: you CAN use finalizers. But it is only a good idea as a failsafe for bad code that has failed to close the db connection [16:26:42] <BadApe> Sticky, thanks, i think i don't mind having to remember so much [16:27:33] <Sticky> and you should probably log that you have a bug if you hit a contition where a finilizer has to clean up the db connection [16:50:15] * ChanServ sets mode: +o temporalfox

[17:53:31] * ChanServ sets mode: +o temporalfox [23:51:37] * ChanServ sets mode: +o temporalfox