The short answer is no. Memcached is a cache. What you want is a queue, and if you do a quick scan of the list archives, you'll find there was a good discussion of this topic ( http://groups.google.com/group/memcached/browse_thread/thread/6e1c7f1fa6482270/31715c9833ef4c04?lnk=gst&q=queue#31715c9833ef4c04)<http://groups.google.com/group/memcached/browse_thread/thread/6e1c7f1fa6482270/31715c9833ef4c04?lnk=gst&q=queue#31715c9833ef4c04>
On Wed, Oct 29, 2008 at 3:31 PM, outinsun <[EMAIL PROTECTED]> wrote: > > I am building an application using SOA. I have one service that needs > to embed infrequently updated information that is managed by another > service. I want to avoid having to make RPC calls every time I access > the data in question, but also want to make sure updates to that data > are reflected at the other end. I can't figure out whether memcached > is a logical basis for this kind of application, or is completely > irrelevant. Any thoughts? If irrelevant, any pointers to something > more appropriate? -- "If you see a whole thing - it seems that it's always beautiful. Planets, lives... But up close a world's all dirt and rocks. And day to day, life's a hard job, you get tired, you lose the pattern." Ursula K. Le Guin http://www.finsel.com/words,-words,-words.aspx (My blog) - http://www.finsel.com/photo-gallery.aspx (My Photogallery) - http://www.reluctantdba.com/dbas-and-programmers/blog.aspx (My Professional Blog)
