Now there's definitely a good reason to remove the dependency on the Yaws arg. It shouldn't be too hard -- I think the only internal dependency is where ErlyWeb inspects the appmod to derive the requested component. If anyone wishes to use ErlyWeb with MochiWeb, it would be great it they took on this little project and contributed their work. (I've already started using Yaws for Vimagi, so I don't want to go through the trouble of switching, but MochiWeb does look like a great alternative for new apps.)
On Nov 11, 2007 10:15 PM, Robin <[EMAIL PROTECTED]> wrote: > > MochiWeb was recently open sourced: > > Announcement: > http://bob.pythonmac.org/archives/2007/11/07/mochiweb-another-faster-web-server/ > > Google Code: > http://code.google.com/p/mochiweb/ > > Google Group: > http://groups.google.com/group/mochiweb > > ErlyMochiWeb anyone? > > > On Sep 27, 2:00 am, Robin <[EMAIL PROTECTED]> wrote: > > Hey Bob, mochiweb could be a nice lightweight container for erlyweb > > apps, any hint when you will 'properly' open source it? > > > > On Sep 26, 11:30 pm, "Bob Ippolito" <[EMAIL PROTECTED]> wrote: > > > > > Before we switched from yaws to mochiweb, we had a module "mochiyaws" > > > that had accessor functions for the yaws arg such that we could return > > > something consistent regardless of the yaws version and without > > > polluting the rest of our code with yaws include files. > > > > > -bob > > > > > On 9/26/07, Yariv Sadan <[EMAIL PROTECTED]> wrote: > > > > > > Ugh, it's really annoying how every Yaws version treats the appmod > > > > differently. However, I'm a bit wary of breaking existing apps by > > > > passing something different from the arg. Also, supporting other web > > > > servers using an adapter sounds like a good concept, but I'm not sure > > > > than in practice anyone needs it. Please correct me if I'm wrong. > > > > > > Yariv > > > > > > On 9/25/07, Robin <[EMAIL PROTECTED]> wrote: > > > > > > > Hey Yariv! This is the same Robin from Erlounge... > > > > > > > Ironically, tonight I am using the new Yaws 1.71 and ErlyWeb 0.6.2 is > > > > > now adding an extra '/' in the paths. > > > > > > >http://localhost:3000/blog//post/list/1 > > > > >http://localhost:3000/blog//post/new > > > > >http://localhost:3000/blog//post/edit/1 > > > > >http://localhost:3000/blog//post/edit/2 > > > > > > > (note the extra '/' on all the paths) > > > > > > > start_yaws()-> > > > > > code:add_patha("/opt/local/lib/yaws/ebin"), > > > > > code:add_patha("./apps/blog/ebin"), > > > > > erlyweb:compile("./apps/blog",[{auto_compile, > > > > > true},{erlydb_driver, > > > > > mnesia }]), > > > > > yaws:start_embedded("./apps/blog/www",[{servername, > > > > > "localhost"}, > > > > > {port, 3000}, > > > > > > > > > > {appmods,[{"blog",erlyweb}]}, > > > > > > > > > > {opaque,[{"appname",blog}]}, > > > > > > > > > > {allowed_scripts,[]}], > > > > > > > > > > [{logdir,"./log"}]). > > > > > > > The problem could be caused by unfiltered use of the Yaws args, but I > > > > > have not debugged it yet. > > > > > > > Back to the topic... > > > > > > > You are right that Erlyweb does not need all the fields of Yaws arg. > > > > > The Yaws arg seems to have lots of unused fields that get carried > > > > > around inside Erlyweb. > > > > > > > Using an ErlyWeb record that is adapted from a filtered version of the > > > > > Yaws arg would help isolate future modifications to the adapter code > > > > > when Yaws arg changes. > > > > > > > Also, adapters could be made to support other web servers. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
