> Whoops. Knew I forgot something. I second this. I don't think this would > be too hard - someone correct me if I'm wrong. Erlyweb would only need > to have a couple of new HTTP methods added on top of the GET/POST > already supported which mean doing something like > > case yaws_arg:method(A) of > 'POST' -> do_something1; > 'GET' -> do_something2; > 'PUT' -> do_something3; > 'DELETE' -> do_something4; > _ -> oops > end > > in your app_controller or where ever you needed to differentiate between > the methods. Now, I haven't been playing with erlyweb of late so the > foregoing is most likely wrong-ish at best.
As I suggested before, you can do this in the hook/1 function. Just rewrite the appmoddata field of the arg before passing it down to ErlyWeb. Yariv --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
