On Fri, Dec 3, 2010 at 1:08 PM, Daniel Lyons <[email protected]> wrote: > This looks much cleaner than I was expecting for the amount of > effort. I am glad I asked! Are you planning on integrating > snap-extensions into Snap later on?
Yes, it will be in before we release 0.3. > I'm currently having trouble building snap-extensions, by the way: > > [11 of 12] Compiling Snap.Extension.Server ( > src/Snap/Extension/Server.hs, dist/build/Snap/Extension/Server.o ) > > src/Snap/Extension/Server.hs:135:26: Not in scope: `getAddress' > > src/Snap/Extension/Server.hs:136:26: Not in scope: `getPort' > > cabal: Error: some packages failed to install: > snap-extensions-0.1 failed during the building phase. The exception was: > ExitFailure 1 It looks like snap-extensions hasn't been kept in sync with more recent changes to Snap. I think that code is getting the IP address and port that the server is listening on. If you look at the Config and ConfigListen data types defined at https://github.com/snapframework/snap-server/blob/master/src/Snap/Http/Server/Config.hs#L67 you'll see that this probably needs to be changed to get the data from Config's listen field. It might help to look at the commit history for this file to see how things changed in the past. I don't have time to fix this right now. Hopefully it points you in the right direction so you can fix it yourself. It should be a fairly straightforward change. _______________________________________________ Snap mailing list [email protected] http://mailman-mail5.webfaction.com/listinfo/snap
