Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 1.1.0.RC1
    • Component/s: GWT
    • Labels:
      None

      Description

      Discussion and assumptions so far:

      • per request cache, based on equality of request objects
      • write through cache
      • poison cache after any write (perhaps narrow this to records of the same type as that written)
      • some heuristics about what looks like a write (merge() and persist()? any instance method?)
      • @CacheHint type of annotation to allow user explicit control

      and don't forget about using HTML5 db when it's available, although there are UI concerns there (must not do it w/o getting user permission)

        Attachments

          Activity

            People

            Assignee:
            amitmanjhi@google.com Amit Manjhi
            Reporter:
            rjrjr@google.com Ray Ryan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2d
                2d
                Remaining:
                Remaining Estimate - 2d
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified