Comments on: Managing State in CAB Smart Clients http://laribee.com/managing-state-in-cab-smart-clients There are eight million stories in Cloud City; this is just one. Tue, 09 Mar 2010 19:48:21 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Reno Jackson http://laribee.com/managing-state-in-cab-smart-clients/comment-page-1#comment-76 Reno Jackson Sat, 09 Jan 2010 12:33:18 +0000 http://laribee.com/blog/2006/10/31/managing-state-in-cab-smart-clients/#comment-76 I understand what you are trying to say here. I too have a problem with CAB that has plagued it since its inception. Its in-process and standalone nature does not allow it to scale beyond a certain point. Integrity issues pop up and the best option is not to use it altogether. All this is better explained here: <a href="http://www.alachisoft.com/ncache/caching-application-block_index.html" rel="nofollow">http://www.alachisoft.com/ncache/caching-applic...</a> I understand what you are trying to say here. I too have a problem with CAB that has plagued it since its inception. Its in-process and standalone nature does not allow it to scale beyond a certain point. Integrity issues pop up and the best option is not to use it altogether. All this is better explained here: http://www.alachisoft.com/ncache/caching-applic...

]]> By: Paul Schofield http://laribee.com/managing-state-in-cab-smart-clients/comment-page-1#comment-75 Paul Schofield Fri, 19 Sep 2008 10:40:50 +0000 http://laribee.com/blog/2006/10/31/managing-state-in-cab-smart-clients/#comment-75 I've been scouring blogs looking for practical in-depth guidance for CAB in real-life applications. Thank you for delving into this topic! One question that I can't seem to find advice on is this: if the Presenter needs to fetch data from different services (or re-use data already in memory) depending on the use case, would it make sense in that scenario to factor out the use case-specific logic into separate WorkItem controllers? I feel a little guilty making service calls inside a SmartPart, as there could always be a new use case in which the SmartPart does not persist its data, but leaves that up to the WorkItem controller. It feels like persistence is use-case-specific to me. I would be interested in hearing your thoughts. I’ve been scouring blogs looking for practical in-depth guidance for CAB in real-life applications. Thank you for delving into this topic!

One question that I can’t seem to find advice on is this: if the Presenter needs to fetch data from different services (or re-use data already in memory) depending on the use case, would it make sense in that scenario to factor out the use case-specific logic into separate WorkItem controllers? I feel a little guilty making service calls inside a SmartPart, as there could always be a new use case in which the SmartPart does not persist its data, but leaves that up to the WorkItem controller. It feels like persistence is use-case-specific to me.

I would be interested in hearing your thoughts.

]]> By: edgelttrind http://laribee.com/managing-state-in-cab-smart-clients/comment-page-1#comment-74 edgelttrind Thu, 06 Sep 2007 21:09:35 +0000 http://laribee.com/blog/2006/10/31/managing-state-in-cab-smart-clients/#comment-74 http://free-sex-lolita-tgp.com/lolita-zoo-tgp.html lolita zoo tgp http://free-sex-lolita-tgp.com/lolita-zoo-tgp.html lolita zoo tgp

]]>