Hey Gaetano, 2012/11/12 Gaetano Mendola <mend...@gmail.com>: > This means that without the wApp->bind there is the possibility that > a widget (with the same span-life of the session) could have been > destroyed while the > session still exists?
Unless the widget (or object) has the same life-span as the session, i.e. is being deleted only together with your application session, you need wApp->bind() to guarantee correct delivery to a living widget. If you can guarantee this matching life-span, then indeed there is no need or use for WApplication::bind() But for a really useful reusable widget, you'll want your widget to be used as the user likes ? Regards, koen ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
