One way to "sandbox" applications would be to use ErlHive. http://erlhive.sourceforge.net/
http://code.google.com/p/erlhive/wiki/ErlhiveUserGuide You can see an example of how it could look when calling into erlhive from a yaws-based application (not using ErlyWeb) in http://erlhive.svn.sourceforge.net/viewvc/erlhive/trunk/lib/nofrills/src/blog.erl?revision=57&view=markup 85 auth_do(Who, Mod, Args) -> 86 ... 89 Val = case check_args(Args) of 90 true -> 91 erlhive:with_user(Who, 92 fun(M) -> 93 M:apply(Who, top_blog, 94 main_auth, [Mod,Who,Args]) 95 end); 96 false -> ... 98 end, 99 [{html, Val}]. In this case, the full name of the actual module called by erlhive is going to be erlhive.<Who>.top_blog Erlhive does put some restrictions on what code can be in the modules, but it's fairly liberal. There is also a 'trusted' flag that allows you to break out of the sandbox. It may be overkill for your needs, but it does solve the problem you mentioned. BR, Ulf W 2008/11/4 Dmitrii Dimandt <[EMAIL PROTECTED]>: > > This is a problem I ran into with ErlyWeb, but I guess this affects all > other apps running under yaws. > > If I have a component named main_controller.erl in app A and another > component named main_controller.erl in app B, they will clash. That is, the > servere will only pickup the most recently compiled component (so it seems > though I can be completely wrong). > > Is there a way to "sandbox" these apps, to shield them from each other? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
