search

tunnckoCore / ideas

:notebook: My centralized place for ideas, thoughts and todos. Raw, PoC implementations and so on... :star:
http://j.mp/1stW47C
6 stars 0 forks source link

choky - Fullstack framework, built on koa.io (koa + socket.io) and choo? #52

Open tunnckoCore opened 7 years ago

tunnckoCore commented 7 years ago

Before few months I got access to koa.io from previous maintainer, so.. I should find some time to start from somewhere. I'm thinking directly to use koa@2. Also when it is almost stable, we can start building choky.

tunnckoCore commented 7 years ago

So... more thoughts came to my head.

I don't like idea my models to be in the client, huh? So I'm thinking for client-side router + views and server-side router + models (+ controllers).

In development, you have one src dir for example where is your views/components/elements for the client, bundle them. You starts the koa server with router + controllers, outputs the bundle in the client. In some action or some route, or something you send data through socket.io to the server to some route, that route handles the request -> pass it to controller, controller does his job -> pass to model -> back to ctrl -> from controller pass through sockets to the client-side router + client controllers -> client controllers pass to client views.

tunnckoCore commented 7 years ago

Okey. More thoughts.

Just seen through the notifications the name hapi-riot and read the README. Then I thought for something like koa-choo - okey. Then while thinking.. I said:

Okey... views on server.. mm okey, so we should update koa-bel (there might be some issues) so.. why not gana on server? - we removing one core part from choo; Then, I'm against models on client - we removing another part from choo. So it just remains the router.. nah it is unassertify-ied.. nah, so we totally remove everything from choo ;d

So finally what? We just need awesome and stable client router. Which in turn will use client controller. This controller will point to server router. Server router uses server controller. Server controller communicates with the server views (gana) and the server models.

Where is the realtime? The perfect place will be the bridge between the client controller(s) and server controllers (actually the server router).

tunnckoCore commented 7 years ago

choo/issues/336