These are chat archives for synrc/n2o

29th
Oct 2015
Maruthavanan Subbaryan
@marutha
Oct 29 2015 02:00
@aseidlitz I agree, what I thought was process of rendering of html components at client side rather than server side can distribute the process to client and server will have less work, let server jus provide data which client cannot access and do rest in client like many other applications. and I also had doubt why we should open websocket each time when a page is requested, Any idea how SPA can be implemented any routers available? Sorry that I am not a proficient JS guy, asking this out of curiosity. Excuses.
Andy
@m-2k
Oct 29 2015 02:55
Use server-side rendering and history api for navigate to pages without sending html get-request to server, only one ws connection for all time
Andy
@m-2k
Oct 29 2015 03:00
Dom updating over ws connections is very fast
You should not want to send the data to the browser with the of another api and rendering on the client side, partially taking out the business logic to the client side
likely will bottle neck speed of access to the database on the server side rather than rendering
Maruthavanan Subbaryan
@marutha
Oct 29 2015 04:06
Sounds good, let me revisit things again in N2o, Yes I completely agree that data has to be provided via API. if Updating Dom is easy, I shall try few things and get back if I need some help.
Thanks a lot for your inputs.
Maruthavanan Subbaryan
@marutha
Oct 29 2015 14:51
It was great to working with N2O, I am curios to know how filtering of data can be done? Should this be done in server side as well? I tried with a basic application. I was looking for providing sorting and filtering options to user. Should I make use of server side events over websockets?
Andy
@m-2k
Oct 29 2015 15:03
kvs:fold/7?
Maruthavanan Subbaryan
@marutha
Oct 29 2015 15:16
You mean to say I have to do the filtering at server?
Andy
@m-2k
Oct 29 2015 15:17
It depends on the task
But why not?
also you can sort by the simultaneous addition of records in different tables, and then read the appropriate
Denys
@denys-potapov
Oct 29 2015 16:10
Всем привет!
я пишу статью, о n2o для тех кто не знаком с ерлангом
и я хочу, чтобы кто-то посмотрел код к статье?
выдержал ли он в духе н2о? и так ли надо было решать задачу с блогом и комментариями?
Andy
@m-2k
Oct 29 2015 16:19
Посмотрю через час
Denys
@denys-potapov
Oct 29 2015 16:29
ок, спасибо - я через час не буду в гиттере, но вечером все прочитаю и учту
Alex Popov
@aseidlitz
Oct 29 2015 18:05
@denys-potapov У меня FB аутенфикация не работает: "App Not Setup: This app is still in development mode, and you don't have access to it. Switch to a registered test user or ask an app admin for permissions." Надо сделать приложение публичным.
@denys-potapov кроме того у меня ошибки в консоле сыпятся:
=ERROR REPORT==== 29-Oct-2015::10:57:29 ===
n2o_nitrogen:Event Init: error:function_clause
[{index,event,[init],27},
{n2o_nitrogen,info,3,21},
{n2o_proto,push,5,38},
{n2o_stream,websocket_handle,3,38},
{cowboy_websocket,handler_call,7,588},
{cowboy_protocol,resume,6,457}]
=ERROR REPORT==== 29-Oct-2015::10:57:35 ===
n2o_nitrogen:Catch: error:function_clause
[{index,event,[[]],27},
{n2o_nitrogen,html_events,2,70},
{n2o_nitrogen,info,3,32},
{n2o_proto,push,5,38},
{n2o_stream,websocket_handle,3,38},
{cowboy_websocket,handler_call,7,588},
{cowboy_protocol,resume,6,457}]
=ERROR REPORT==== 29-Oct-2015::10:57:35 ===
n2o_nitrogen:Event Init: error:undef
[{login,event,[init],undefined},
{n2o_nitrogen,info,3,21},
{n2o_proto,push,5,38},
{n2o_stream,websocket_handle,3,38},
{cowboy_websocket,handler_call,7,588},
{cowboy_protocol,resume,6,457}]
Andy
@m-2k
Oct 29 2015 18:24
код вроде ок
только его как-то подозрительно мало для бложика :smile:
Namdak Tonpa
@5HT
Oct 29 2015 20:09
код нормальный