://old.nabble.com/wicketstuff-push-and-component-replacing-tp27274128p27435497.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail
(809) 860-6669
--
View this message in context:
http://old.nabble.com/wicketstuff-push-and-component-replacing-tp27274128p27435497.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e
CTO, KindleIT Software Development
Email: rhan...@kindleit.net
Mobile: +1 (809) 860-6669
--
View this message in context:
http://old.nabble.com/wicketstuff-push-and-component-replacing-tp27274128p27435497.html
Sent from the Wicket - User mailing list archive at Nabble.com
I have basically concentrated on the CometD Service
This should be a simple bug to fix.
On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares roland.va...@uptime.eewrote:
Hello,
I'm currently developing wicket based application, which displays alarms on
map and allows their modification.
New
Try now...
To me, the push service is overly complicated, and you could easily get away
with simply using Wicket's AjaxTimeoutBehavior as there are no technical
advantages over the later.
The comet version of push offers a couple of serious advantages for the
server, and client side. Why can't
Hello,
I'm currently developing wicket based application, which displays alarms on map
and allows their modification.
New alarms are sent to server through soap service and map with few other
components on page for all browser clients needs to be refreshed.
I'm using wicketstuff-push for the
