Makes sense, thanks for the reply.
Another thing that is odd. I seem to have trouble while rendering
eventLinks inside a block that is a delagate of a pushTarget.
in tml:
a bunch of html markup
in the java class
public Block getTokenPlayHistoryBlock(){
switch based on conditions
Hi,
I've been reading through the JavaScript changes in tapestry 5.4 and the
use AMD in particular. I was able to load my custom module and other
libraries as described in documentation here :
http://tapestry.apache.org/client-side-javascript.html and here:
http://tapestry.apache.org/javascript-mo
The disconnect event is fired by atmosphere under the hood
(AtmosphereResourceEventListener.onDisconnect). Further reading here:
https://github.com/Atmosphere/atmosphere/wiki/onDisconnect-tricks
http://atmosphere.github.io/atmosphere/apidocs/org/atmosphere/cpr/AtmosphereResourceEventListener.html
Sure I will start with that. Will keep you posted. Thanks for the help
On Sat, Jun 14, 2014 at 9:55 PM, Lance Java
wrote:
> > what would be the fix?
> Let's see the network traffic first. It's like asking your doctor for
> medicine before telling him your symptoms ;)
> On 14 Jun 2014 18:58, "B
