Sounds to me like a benchmark is needed to compare id lookup against full DOM
scan for data attributes on all the major browsers on small, medium and
large web pages.
--
View this message in context:
On Thu, 08 Nov 2012 05:25:15 -0200, Javicha javilan...@gmail.com wrote:
I was wrong, Tapestry version is 5.1.0.5 (not 5.0).
And I have found that @Persist if shared between sessions (I do a search
by name 'Peter'. I log out. I log on with a different user session. I go
to the search page,
Here's a first attempt at benchmarking the differences:
http://jsfiddle.net/xPVy6/6/
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/5-4-JavaScript-Explicit-vs-Unobtrusive-initialization-tp5717787p5717818.html
Sent from the Tapestry - Dev mailing list archive at
If I understand your question correctly you are trying to figure out if it's
better to initialize the javascript elements on the client side by id or by
some other kind of selector.
I use both Bootstrap and the Facebook apis and they both use data elements
and then automatically initialize the
How did you do the log out part?
As Thiagos says, it could be that your session is still valid. Try using 2
different browsers (not windows or tabs) and see if the problem disappears.
Regards
Sigbjørn Tvedt
On 8 November 2012 11:14, Thiago H de Paula Figueiredo
thiag...@gmail.comwrote:
On
I modified the fiddle to loop 100 times; this will partially account for
cachine, and MV optimizations. By the last round:
idLookup: 2ms
dataLookup: 15ms
Still, tiny amounts of time.
On Thu, Nov 8, 2012 at 4:45 AM, Lance Java lance.j...@googlemail.comwrote:
Here's a first attempt at
On Thu, 08 Nov 2012 15:32:56 -0200, Howard Lewis Ship hls...@gmail.com
wrote:
I modified the fiddle to loop 100 times; this will partially account for
cachine, and MV optimizations. By the last round:
idLookup: 2ms
dataLookup: 15ms
Still, tiny amounts of time.
Which browser? Anyway, even
Maybe Tapestry should automatically display a Switch to Chrome alert if
it detects IE :-)
On Thu, Nov 8, 2012 at 10:32 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Thu, 08 Nov 2012 15:32:56 -0200, Howard Lewis Ship hls...@gmail.com
wrote:
I modified the fiddle to loop 100
My logout method is:
@Property
@SessionState(create = false)
private UserSession userSession;
@AuthenticationPolicy(AuthenticationPolicyType.AUTHENTICATED_USERS)
Object onActionFromLogout() {
userSession = null;
