While speaking at the Globalcode Developer's conference in Rio de Janeiro, I met a dynamic and intelligent student by the name of Thiago Diogo. Thiaogo presented his group's work on student project to provide a real, mission critical distributed application for his university, Universidade Federal Fulminense. They chose JSF 1.2 and Seam as a part of their stack.

One idea Thiaogo shared with me was a memcachedJSF component. We kicked the idea around and I mentioned it would be pretty easy to invent a JSF component that acted like a<span> tag that simply meant, “the rendered output of any JSF components inside of me should come from memcached, if possible”. I don't have time to start on this idea right now, so I thought I'd share it out here in my blog in case anyone else wanted to pick it up, or if anyone else has already done this! When I get time, I'll try adding it to the Mojarra sandbox components, but in the meantime, anyone can have at it!

Technorati Tags: edburns

4 Comments

  • pmuir Newbie

    pmuir Nov 23, 2009 11:14 PM

    Ed, one of the components we have always had in Seam was the tag, which rendered any nested tags using cached output (we never ventured into allowing input components inside these regions, not sure if that is something you are envisaging?). Anyway, a mistake we made early on was to essentially tie the component to the JBoss Cache API (which we later retrofitted to a generic API). As a result I would recommend not tying yourself to any particular API, but instead use a neutral one. In general, Map is a great fit for a cache access (and maybe ConcurrentMap for adding stuff to the cache), so I would suggest using that. You could then provide a default implementation based on memcached (which is definitely a pseudo-standard API :-) //
    • thiagodiogo Newbie

      thiagodiogo Nov 25, 2009 12:51 AM

      • dnamiot Newbie

        dnamiot Nov 28, 2009 11:07 PM

        check out this for example: http://www.servletsuite.com/servlets/cachetag.htm //