Well remember, there is no Erlang view server, there is a *native* view server.
You can spawn a named process and ! and receive all day long. You can spawn a gen_server or a whole application. You can also store functions in named ets tables. If you have a cluster then you may need to re-define them. The usual "doesn't work in a cluster" warnings apply I suppose. Sounds like fun. But as Paul says, be careful! On Thu, Oct 6, 2011 at 5:06 AM, Thomas Van de Velde <[email protected]> wrote: > I am mostly interested in sharing between a show and list as both can > generate similar outputs. > > On Wed, Oct 5, 2011 at 4:53 PM, Ryan Ramage <[email protected]> wrote: > >> Great, this is just the hole we need to call external services, make >> requests, hot swap code, etc! >> >> oh wait, and screw up the view by making it non referentially >> transparent! :) I think Paul really meant *quite* careful. >> >> On Wed, Oct 5, 2011 at 3:42 PM, Paul Davis <[email protected]> >> wrote: >> > Erlang code doesn't have a commonJS equivalent. If you were to put >> > code on the Erlang path you could reference it, but you'd want to be >> > *quite* careful about doing this for views. >> > >> > On Wed, Oct 5, 2011 at 4:08 PM, Thomas Van de Velde >> > <[email protected]> wrote: >> >> Hi, >> >> >> >> How can I reference an external module from within a view, show or list? >> >> This would be to reuse code. >> >> >> >> Thanks! >> >> >> >> Thomas >> >> >> > >> > -- Iris Couch
