Hmmm what about a prefix of the same length than currently to prevent page size increase, but a bit strange to prevent most potential clashes? Maybe i_d?
On 4/20/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
On Apr 20, 2007, at 12:24 PM, Mario Ivankovits wrote: Belen, Marco wrote: In order 'choose' an unique prefix, why not re-use a common way to create unique names in Java: Use a package-structure. There for until it can be configured in the web.xml how about using "org_apache_myfaces_" as the clientID-prefix. My first reaction on this was: "No, please don't" as this will greatly increase the size of the rendered html page if you have tables or trees on it. On the other hand, if one would like to have short ids its simple to configure the id on the component level instead of using the autogenerated one - and IMHO its better to use manual component ids then the automatic created one as this makes the rendered page more readable (in case you have to look at the html source) So I'll have not problem to use this "big" clientId, just, maybe a "o_a_m_id" would make it too. I had the same reaction about how this change could increase the size of the rendered page. True that it could be configured at the component level, but for the sake of performance how about taking a position that the autogenerated one is as small as reasonably possible and rely on the user to replace it in the case of a collision? i.e. the user optionally lengthens, not shortens, the autogenerated id. Best wishes, Paul
