ANNOUNCE: Slinky 2.1

So, what you're saying is that if the web frameworks for Scala merged, they'd be called Sweet Slinky Lift? :-)
Congratulations.

On Thu, Dec 18, 2008 at 9:42 PM, Tony Morris <tmorris@tmorris.net> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Speaking of announcements we have been using a HTTP library for our
commercial web development for some time. A small overview; a web
application is a function Request => Response based on RFC2616 with a
library of combinators for putting together handlers for these requests.

Homepage:
http://code.google.com/p/slinky2/

Google Group:
http://groups.google.com/group/slinky

Example application:
http://code.google.com/p/slinky2/source/browse/trunk/demo/src/main/slinky/demo/App.scala

- --
Tony Morris
http://tmorris.net/

S, K and I ought to be enough for anybody.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJSzQ4mnpgrYe6r60RAtpLAJ4tRLHk4C8lx7S15kMy3Tk6zgwp4gCgiKTS
KVQ14iNLcY6+HCBJ4s5AaGc=
=uVOJ
-----END PGP SIGNATURE-----

--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

Hi Tony,

Somehow I missed this announcement until now. I took a quick look at
Slinky. It reminded me a bit of the architecture we made for new
Artima stuff in Java several years back, to make it easier to test our
web functionality. We pass in a request and get back a response object
that hasn't actually done anything yet, so we can test it more easily.
We then can invoke a method on the response object to get it to write
to the socket, or if it's a test just look at the info it contains.

You talk about side effects on the web page:

Slinky is a HTTP library for web applications using the Scala
Programming Language. It models a web application as a function ::
Request -> Response rather than the more typical side-effecting
procedure that accepts both a Request and Response to perform effects
on the response.

But in most webapps there's also the database involved. We do read
from the database usually on most requests, but if it is a POST it
isn't actually written to until later because the commit happens at
the very end of the process. But since we're going through Hibernate
it looks as if we are doing side effects in the process of handling
the POST, so do you do the same kind of thing when you're using
slinky? How do you deal with updating the database?

Bill

On Thu, Dec 18, 2008 at 9:42 PM, Tony Morris wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Speaking of announcements we have been using a HTTP library for our
> commercial web development for some time. A small overview; a web
> application is a function Request => Response based on RFC2616 with a
> library of combinators for putting together handlers for these requests.
>
> Homepage:
> http://code.google.com/p/slinky2/
>
> Google Group:
> http://groups.google.com/group/slinky
>
> Example application:
> http://code.google.com/p/slinky2/source/browse/trunk/demo/src/main/slink...
>
> - --
> Tony Morris
> http://tmorris.net/
>
> S, K and I ought to be enough for anybody.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFJSzQ4mnpgrYe6r60RAtpLAJ4tRLHk4C8lx7S15kMy3Tk6zgwp4gCgiKTS
> KVQ14iNLcY6+HCBJ4s5AaGc=
> =uVOJ
> -----END PGP SIGNATURE-----
>
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Bill,
Yes the database does indeed cause another problem. I have started
working on solving this in scalaz.database by replicating an API
similar to LINQ. Specifically, scalaz.database.Database is a monad
that sets the foundation for implementing a relational algebra inside of.

Speaking of tests,
http://slinky2.googlecode.com/svn/trunk/demo/src/test/slinky/demo/Tests....
are the tests for
http://slinky2.googlecode.com/svn/trunk/demo/src/main/slinky/demo/App.scala

Bill Venners wrote:
> Hi Tony,
>
> Somehow I missed this announcement until now. I took a quick look
> at Slinky. It reminded me a bit of the architecture we made for new
> Artima stuff in Java several years back, to make it easier to test
> our web functionality. We pass in a request and get back a response
> object that hasn't actually done anything yet, so we can test it
> more easily. We then can invoke a method on the response object to
> get it to write to the socket, or if it's a test just look at the
> info it contains.
>
> You talk about side effects on the web page:
>
> Slinky is a HTTP library for web applications using the Scala
> Programming Language. It models a web application as a function ::
> Request -> Response rather than the more typical side-effecting
> procedure that accepts both a Request and Response to perform
> effects on the response.
>
> But in most webapps there's also the database involved. We do read
> from the database usually on most requests, but if it is a POST it
> isn't actually written to until later because the commit happens at
> the very end of the process. But since we're going through
> Hibernate it looks as if we are doing side effects in the process
> of handling the POST, so do you do the same kind of thing when
> you're using slinky? How do you deal with updating the database?
>
> Bill
>
> On Thu, Dec 18, 2008 at 9:42 PM, Tony Morris
> wrote: Speaking of announcements we have been using a HTTP library
> for our commercial web development for some time. A small overview;
> a web application is a function Request => Response based on
> RFC2616 with a library of combinators for putting together handlers
> for these requests.
>
> Homepage: http://code.google.com/p/slinky2/
>
> Google Group: http://groups.google.com/group/slinky
>
> Example application:
> http://code.google.com/p/slinky2/source/browse/trunk/demo/src/main/slink...
>
>
>>
>>

- --
Tony Morris
http://tmorris.net/

S, K and I ought to be enough for anybody.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJTUh7mnpgrYe6r60RAtkDAJkB8PWkBv+9fsa1IpRwN6YcpwyHsgCeMsBT
806xO4xproRFFD1HPainO70=
=CPJz
-----END PGP SIGNATURE-----