nimforum mirror - server-client webframework

choltreppe (orginal) [2022-03-23T01:26:24+01:00] view original

Hi there,

I just very recently stumbled upon nim, and I realy like it.

And one thing I would like to have for nim is a client+server webframework. (like OCamls ocsigen or ur/web or opa-lang) So i decided to take initiative, and started writing something like that:

https://github.com/choltreppe/nim_serclim

Im not very experienced in writing libraries and there is still a lot missing. So every help to make this a real production ready thing is very welcome.

greetings Joel

dom96 (orginal) [2022-03-23T12:46:32+01:00] view original

Looks amazing! Nim is definitely a language that needs something like this. Thank you for taking the initiative to build it :)

PMunch (orginal) [2022-03-23T12:59:54+01:00] view original

This looks really cool, it's one of those projects I've wanted to have a go at ever since I found Nim but never found the time to do.

jasonfi (orginal) [2022-03-23T14:46:33+01:00] view original

I'm working on a server/client framework myself, but with a Flutter engine on the client: https://nexusdev.tools/

I would like to release an initial code drop sometime next month.

nepeckman (orginal) [2022-03-23T15:10:41+01:00] view original

I worked on a similar project a while back, no idea if any of my code is applicable for your purposes but feel free to copy anything helpful :)

https://github.com/nepeckman/nerve-rpc

choltreppe (orginal) [2022-03-23T18:11:25+01:00] view original

That looks intressting. ill defintly have a look at it when you release

choltreppe (orginal) [2022-03-23T18:11:58+01:00] view original

thanks. ill have a look at it

jwatson-CO-edu (orginal) [2022-04-13T20:10:42+02:00] view original

@nepeckman , can you give us some examples of where you have used this library?

reversem3 (orginal) [2022-04-19T21:13:29+02:00] view original

excuse my ignorance but what makes this web-framework different then say , prologue , jester, the dozens of other web frameworks on nimble.directory?

PMunch (orginal) [2022-04-20T08:57:17+02:00] view original

It focuses on a tighter binding between front- and back-end. Essentially it only targets browsers with JavaScript capabilities where e.g. Prologue and Jester can be used to create simple REST APIs (this might be able to as well, but the focus seems to be on the client/server interaction). Using this framework all the code for your site is in one project, not split in server and client. The client can call procedures defined on the server and those are executed through some RPC system. This probably means that it is (or at least that it could be) type checked since it's all one project. It will then compile the project into two parts, one binary and one JavaScript output, the latter of which could simply be stored directly in the binary as the result to some route. The benefits of such a system is of course that you get everything in one place, which enables type safety and the same "if it compiles it works" idea that you enjoy when writing other projects in Nim. The downside is that it is probably quite a bit more opinionated than something like Jester or Prologue (but I wouldn't be surprised if it used one of them in the background).

reversem3 (orginal) [2022-04-21T16:25:09+02:00] view original

That was great, thanks for the explanation.

choltreppe (orginal) [2022-04-21T23:46:28+02:00] view original

thanks for explaining. Forgott to look in the forum for some days :/

This probably means that it is (or at least that it could be) type checked since it's all one project.

Yes.

the latter of which could simply be stored directly in the binary as the result to some route.

That would be the better way. But I couldnt figure out how to put the compiler output directly into a string to use for the server. So for now it is compiled into a seperate file. But I will probably change that. If it doesnt work any other way, I could just compile into temp file read it and delete the file or something.

but I wouldn't be surprised if it used one of them in the background

I started with building on top of prologue, with the idea of making it pluggable for any framework in the long run, but that didnt seem to work very elegantly. So I started to write the whole framework from scratch. And used the oportunity to put some ideas from rust/rocket that I realy like into it. ( the routing system that automatically parses the parameters to reduce even more poilerplate)

nepeckman (orginal) [2022-04-22T15:43:54+02:00] view original

I never shipped anything, but I was working on a SPA web app with the following stack: Front end: Karax API: Nerve DB interface: Norm Didn't need much for server side routing because Nerve routes itself and Karax routed the front end.

Dropped the project because I got busy, but I was happy with the way the different libraries interacted.

Lantos (orginal) [2022-08-12T18:51:48+02:00] view original

would be cool to see this if you have the time

Mirror of forum.nim-lang.org

9031 :: server-client webframework