Path: g2news1.google.com!postnews.google.com!k39g2000hsf.googlegroups.com!not-for-mail
From: Hannes Wallnoefer <hann...@gmail.com>
Newsgroups: mozilla.dev.tech.js-engine.rhino
Subject: Re: Metaobject Protocol for JavaScript
Date: Tue, 15 Jan 2008 03:52:54 -0800 (PST)
Organization: http://groups.google.com
Lines: 20
Message-ID: <572c1ce2-0c03-400a-b7eb-b4fcd7e81755@k39g2000hsf.googlegroups.com>
References: <mailman.1394.1198290198.3345.dev-tech-js-engine-rhino@lists.mozilla.org> 
	<a7d90c43-10fb-41ad-b5c0-968eca605d76@v67g2000hse.googlegroups.com>
NNTP-Posting-Host: 85.124.93.178
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1200397975 25610 127.0.0.1 (15 Jan 2008 11:52:55 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 15 Jan 2008 11:52:55 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: k39g2000hsf.googlegroups.com; posting-host=85.124.93.178; 
	posting-account=WkGPRAoAAABr_ifPqXzQxCHX3csEw-KD
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.11) 
	Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11,gzip(gfe),gzip(gfe)

> On Dec 22 2007, 3:23 am, t...@bias2build.com wrote:
>
> > Feedback is welcome.  Am I missing any big pieces in what a MOP should
> > cover?  Does this seem straightforward to use?  I appreciate any insights.
>
> > Thanks, and happy holidays.
>

I did some more testing, comparing your solution with the JSAdapter
approach. I wrote my findings down here:

http://dev.helma.org/wiki/Comparison+of+JSAdapter+and+JOMP/

The problems I see with JOMP is that it adds overhead to each and
every JS object property access, and that it is not thread-safe. Helma
is a multithreaded server application, so concurrent property access
is pretty much the norm. Apart from that, I'd definitely prefer JOMP
over JSAdapter because it feels much more like pure Javascript.

hannes