On Wed, Nov 14, 2012 at 2:42 AM, Matthew Mondor <[email protected]>wrote:
> I forgot to write about another alternative using bytecode though... if
> all code compiles to bytecode only, and the bytecode interpreter
> permits to impose all the limits you need
>
The problem is not the bytecodes, but the libraries. Common Lisp contains
lots of functions that allocate memory. Of course, one could do a very
invasive auditing of ECL and log all those operations, but this is a
nontrivial change -- I doubt this approach is used elsewhere: doesn't
Google Chrome actually devote one process for each page, thus isolating
them perfectly?
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Ecls-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecls-list
