{"issue":{"title":"Fragment class for controller caching","user":{"login":"gazay","id":29658,"url":"https://api.github.com/users/gazay","gravatar_id":"d52cc558a29696bb722492259f3f52de","avatar_url":"https://secure.gravatar.com/avatar/d52cc558a29696bb722492259f3f52de?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-28T04:23:39Z","milestone":null,"labels":[],"state":"open","updated_at":"2011-12-28T04:23:39Z","id":2668993,"closed_at":null,"html_url":"https://github.com/rails/rails/issues/4211","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Hello! I thinking about creating a class for working with cache fragments \r\n\r\nhttps://github.com/rails/rails/commit/71c9337f45f9c5461cbc6ddf6cab764ad0f82c3b#L5R40\r\n\r\nIt's still relevant?\r\n\r\nI want to create something like ActionController::Caching::Fragment class with methods read, write and expire and replace ActionController::Caching::Fragments#read_fragment and write_fragment with find_fragment and create_fragment. \r\n\r\nThere is some sketches: https://gist.github.com/1526231\r\n\r\nWhat do you think? And should we keep objects of Fragment class in controller instance?","number":4211,"url":"https://api.github.com/repos/rails/rails/issues/4211","comments":0,"assignee":null},"action":"opened"}