<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Now it's me not to understand what you mean :)<div>Did you mean to slow down implementing it, or the actual performance of the implementation?</div><div><br></div><div>Implementing it the way Kito suggests, will probably be faster then having to read a context-parameter, even if both solutions will have neglectable impact overall.<br><div><br></div><div>I guess adding two static PropertyDescriptors (with appropriate read-methods) to the property descriptor map wouldn't add any noticeable overhead. Returning null for the write-method will also make them read-only as suggested (this probably should depend on a context-parameter, but would postpone the evaluation of it until a write call is made, which probably no one ever uses)</div><div><br></div><div><br></div><div>Imre<br><div><br><div><div>On 17.08.2010, at 05:06, Blake Sullivan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
This would needlessly slow down the context attributes
implementation, which is also hammered on.<br>
<br>
-- Blake Sullivan<br>
<br>
On 8/16/10 9:10 AM, Kito Mann wrote:
<blockquote cite="mid:AANLkTimYiHML3xx1563fio9MV_1m9HgUrGGDxn70NJ15@mail.gmail.com" type="cite"><br>
<div class="gmail_quote">On Mon, Aug 16, 2010 at 9:48 AM, Ed Burns
<span dir="ltr"><<a moz-do-not-send="true" href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
>>>>> On Wed, 11 Aug 2010 11:46:21 -0400, Kito
Mann <<a moz-do-not-send="true" href="mailto:kito.mann@virtua.com">kito.mann@virtua.com</a>>
said:<br>
<br>
KM> Couldn't you modify the map to return the constant
values for the<br>
KM> proper keys? That way, they would be read-only values
that don't<br>
KM> need to be stored, the Map just needs to know the keys.<br>
<br>
I'm sorry, I don't understand what you mean. Can you please
restate it<br>
differently?<br>
</blockquote>
<div><br>
</div>
<div>Basically, what I'm saying is that we could change the Map
implementation to simply delegate to <span class="Apple-style-span" style="font-family:
arial,sans-serif; font-size: 13px; border-collapse:
collapse;">UIComponent.getCurrentComponent() and </span><span class="Apple-style-span" style="font-family:
arial,sans-serif; font-size: 13px; border-collapse:
collapse;">UIComponent.getCurrentCompositeComponent() in the
get() method whenever the key value is CURRENT_COMPONENT or
CURRENT_COMPOSITE_COMPONENT. This way we'd save space but
would maintain backwards compatibility without the switch. </span></div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<br>
Ed<br>
<font color="#888888">--<br>
| <a moz-do-not-send="true" href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>
| office: +1 407 458 0017<br>
| homepage: | <a moz-do-not-send="true" href="http://ridingthecrest.com/" target="_blank">http://ridingthecrest.com/</a><br>
| 02 work days until JSF 2.1 Milestone 2<br>
</font></blockquote>
</div>
<br>
</blockquote>
<br>
</div>
</blockquote></div><br></div></div></div></body></html>