Re: Making Dylan viable for small web applications?

--===============0289260272==
Content-Type: multipart/alternative; boundary=001a1134735cdae9c405031f4b86

--001a1134735cdae9c405031f4b86
Content-Type: text/plain; charset=UTF-8

I would play around with DSP first, if you haven't yet.  You may get
further than you think.

Bruce wants to basically copy jinja2, which does look pretty good to me.
 I'm interested in helping, as time permits, but I also want to make
testworks able to handle the LLVM test suite again, so that's going to be
my next priority.

I think the biggest problem with http-server is, as Robert pointed out, the
lack of ability to scale.

-Carl

On Sun, Sep 14, 2014 at 11:22 AM, Francesco Ceccon <[email protected]>
wrote:

> Hello,
> I have a couple of ideas for small web applications that I want to develop
> using
> Dylan. I'm not sure about the state of http-server so I'm asking you, if
> something
> is outdated and/or you want it changed I think it's a good opportunity to
> discuss
> it here before working on it.
>
> By looking at projects like Lua's Lapis (http://leafo.net/lapis/) or
> Python's
> Flask and with a quick chat with Bruce I came up with a list of components
> we
> need:
>
> * A web-server, with this I mean the usual routing stuff plus handling
> session etc.
> * Template engine, I know someone is working on it so we should look into
> finishing
>   and/or integrating it with the server
> * Some kind of SQL abstraction layer, at first only supporting SQLite and
>   PostgreSQL would be fine. I'd also like a light ORM, but I think I'm in
> the
>   minority here.
>
> Then we need to figure out to make this components work well together.
>
> Finally, I'd love for the webserver to be extensible, so for example we
> would need
> to write a session-management plugin only once. Bruce talked about
> adopting a
> middleware architecture, but I forgot about it now.
>
> So, what do you think?
>
> -Francesco
> _______________________________________________
> hackers mailing list
> [email protected]
> https://lists.opendylan.org/mailman/listinfo/hackers
>

--001a1134735cdae9c405031f4b86
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would play around with DSP first, if you haven&#39;t yet=
. =C2=A0You may get further than you think.<div><br></div><div>Bruce wants =
to basically copy jinja2, which does look pretty good to me. =C2=A0I&#39;m =
interested in helping, as time permits, but I also want to make testworks a=
ble to handle the LLVM test suite again, so that&#39;s going to be my next =
priority.</div><div><br></div><div>I think the biggest problem with http-se=
rver is, as Robert pointed out, the lack of ability to scale.</div><div><br=
></div><div>-Carl<br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Sep 14, 2014 at 11:22 AM, Francesco Ceccon <span dir=3D"ltr">&l=
t;<a href=3D"mailto:[email protected]" target=3D"_blank">francesco@ceccon=
.me</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
I have a couple of ideas for small web applications that I want to develop =
using<br>
Dylan. I&#39;m not sure about the state of http-server so I&#39;m asking yo=
u, if something<br>
is outdated and/or you want it changed I think it&#39;s a good opportunity =
to discuss<br>
it here before working on it.<br>
<br>
By looking at projects like Lua&#39;s Lapis (<a href=3D"http://leafo.net/la=
pis/" target=3D"_blank">http://leafo.net/lapis/</a>) or Python&#39;s<br>
Flask and with a quick chat with Bruce I came up with a list of components =
we<br>
need:<br>
<br>
* A web-server, with this I mean the usual routing stuff plus handling sess=
ion etc.<br>
* Template engine, I know someone is working on it so we should look into f=
inishing<br>
=C2=A0 and/or integrating it with the server<br>
* Some kind of SQL abstraction layer, at first only supporting SQLite and<b=
r>
=C2=A0 PostgreSQL would be fine. I&#39;d also like a light ORM, but I think=
 I&#39;m in the<br>
=C2=A0 minority here.<br>
<br>
Then we need to figure out to make this components work well together.<br>
<br>
Finally, I&#39;d love for the webserver to be extensible, so for example we=
 would need<br>
to write a session-management plugin only once. Bruce talked about adopting=
 a<br>
middleware architecture, but I forgot about it now.<br>
<br>
So, what do you think?<br>
<br>
-Francesco<br>
_______________________________________________<br>
hackers mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]<=
/a><br>
<a href=3D"https://lists.opendylan.org/mailman/listinfo/hackers" target=3D"=
_blank">https://lists.opendylan.org/mailman/listinfo/hackers</a><br>
</blockquote></div><br></div></div></div>

--001a1134735cdae9c405031f4b86--

--===============0289260272==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers

--===============0289260272==--