Reusing controller data for multiple views RSS

• • Reply
  

  mbhahn

  Member

  169 Points

  119 Posts

  Reusing controller data for multiple views

  Mar 20, 2012 04:07 PM|LINK

  I am using linqtotwitter and I am struggling with a good way to present data without constantly paging the controller and hitting twitter for data.

  With twitter if you do a hit it counts against you whether you get information or not.

  This problem sorta came to my head when i had noticed my page had 2-3 hits per load which isnt good if i have a popular site. 350 requests will go fast.

  How should i store my list so I hit the results not the query each time.

  Outputcache helps but doesnt address my core issue.

  I guess i got sorta 2 problems or 1 depending how you look at it, 

  II have a mvc page with multiple partial views and is working great. 

  Here is a sample for  query.

              List<TweetViewModel> friendstweets = (from tweet in twitterCtx.Status
                                                    where tweet.Type == StatusType.User &&                                         
                                                      tweet.ScreenName == "BattleShouts" &&
                                              //       tweet.InReplyToScreenName == "Battleshouts" &&
                                                    tweet.IncludeEntities == true &&
                                                    tweet.IncludeRetweets == true &&
                                                  tweet.IncludeContributorDetails == true &&
                                                     tweet.CreatedAt < DateTime.Now.AddDays(-30).Date
                                                    select new TweetViewModel
                                                    {
                                                    
                                                        ImageUrl = tweet.User.ProfileImageUrl,
                                                        ScreenName = tweet.User.Identifier.ScreenName,
                                                        Tweet = tweet.Text
                                                    })
       .ToList();
          
   
              return PartialView(friendstweets);
  
  
  

• • Reply
  

  CodeHobo

  All-Star

  18647 Points

  2647 Posts

  Re: Reusing controller data for multiple views

  Mar 20, 2012 04:14 PM|LINK

  What you want to do is Cache the data (in code caching, not output caching) from linqtotwitter. When a user requests data the controller should check the cache first and only pull from twitter if the cache is not there. That way, you can load up a lot of data on the first request and not go to twitter again if you have that data.

  One way to do this elegantly without maknig your controller too complicated is to the linqtotwitter code put it behind a repository class. Then you can use a cached repository pattern to save the data locally to the Cache object. 
  http://ardalis.com/introducing-the-cachedrepository-pattern

  With the cached repository pattern, your controller reads from a single interface and doesn't even know the data is cached, the caching happens at a different layer. 

  Hattan Shobokshi
  Blog | Twitter : @Hattan
  
  • Edited by CodeHobo on Mar 20, 2012 04:14 PM
• • Reply
  

  mbhahn

  Member

  169 Points

  119 Posts

  Re: Reusing controller data for multiple views

  Mar 20, 2012 05:10 PM|LINK

  so basically I was doing another thing wrong in my code practice before i even get started

  In this musicstore code it creates a private list method and passes it to the index controller.  I would need to do the same before i even started on this pattern

          public ActionResult Index()
          {
              // Get most popular albums
              var albums = GetTopSellingAlbums(5);
  
              return View(albums);
          }
  
          private List<Album> GetTopSellingAlbums(int count)
          {
              // Group the order details by album and return
              // the albums with the highest count
  
              return storeDB.Albums
                  .OrderByDescending(a => a.OrderDetails.Count())
                  .Take(count)
                  .ToList();
          }
  
  
  Here is my   Action

        [HttpGet] 
          public ActionResult PublicShouts()
          {
              var Auth = new SingleUserAuthorizer
              {
                  Credentials = new InMemoryCredentials
                  {
                      ConsumerKey = ConfigurationManager.AppSettings["twitterConsumerKey"],
                      ConsumerSecret = ConfigurationManager.AppSettings["twitterConsumerSecret"],
                      OAuthToken = ConfigurationManager.AppSettings["twitterOAuthToken"],
                      AccessToken = ConfigurationManager.AppSettings["twitterAccessToken"]
                  }
              };
              var twitterCtx = new TwitterContext(Auth);
              
          
   
   
   
              List<TweetViewModel> friendstweets = (from tweet in twitterCtx.Status
                                                    where tweet.Type == StatusType.User &&                                         
                                                      tweet.ScreenName == "BattleShouts" &&
                                              //       tweet.InReplyToScreenName == "Battleshouts" &&
                                                    tweet.IncludeEntities == true &&
                                                    tweet.IncludeRetweets == true &&
                                                  tweet.IncludeContributorDetails == true &&
                                                     tweet.CreatedAt < DateTime.Now.AddDays(-30).Date
                                                    select new TweetViewModel
                                                    {
                                                    
                                                        ImageUrl = tweet.User.ProfileImageUrl,
                                                        ScreenName = tweet.User.Identifier.ScreenName,
                                                        Tweet = tweet.Text
                                                    })
       .ToList();
          
  
  I would keep the context and my credential checking in the controller
  
  
  and make a method private List<TweetViewModel> friendstweets ()
  {
  
  Insert the logic
  }
  
  
  Then   Call it with  Context and credential checking and rending the view call
  
  
  
  
  
  Am I overthinking this? The credential checking cannot be cached but i can cache credentials which i did fine