On Mon, 2009-07-27 at 09:01 -0700, S.A. wrote: > Hello, > > We have a requirement of serving fixed set of data elements (text, images, > audio, video, etc) to a group of users coming at about the same time, but > each user requesting different set of data elements from the given data set. > > Data set is fixed, but what data elements are presented to a user is dependent > on user's configuration parameters and they vary from user to user. Other > than the requesting data elements of a given set, there is nothing that > is common among users and hence their requests can be treated as such, ie > as independent requests. > > What is the best way to deal with the above scenario so that the each > httpd process does not goto to either file store or db for each user > request? > > Is there a way that we can retain this data in-memory and depending on > the requesting user, we read their configuration and then come to the > in-memory data set and build a page for the user and serve the user? > > Appreciate any insights or pointers. > > Thanks > S.A. > http://www.danga.com/memcached/ You dont mention what language/mechanism you want to pull the data out; memcached has client libraries for almost every language under the sun, so it should be appropriate. Cheers Tom --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|