Closed Bug 504387 Opened 15 years ago Closed 15 years ago

Cache keys after creating/PUTting them instead of after GETting

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

Attachments

(1 file)

v1
2.21 KB, patch
hello
: review+
Details | Diff | Splinter Review 
Because of 504135, it's possible that we PUT a key and try grabbing it and it doesn't exist. We can work around this by caching them after PUTting.
Attached patch v1 — — Splinter Review 
Assignee: nobody → edilee
Status: NEW → ASSIGNED

        Attachment #389047 -
        Flags: review?(thunder)

    
    

    
  
Comment on attachment 389047 [details] [diff] [review]
v1

r=thunder, except we should also cache the public/private keys.

It doesn't need to be in this patch, but it can be.

        Attachment #389047 -
        Flags: review?(thunder) → review+

    
    

    
  
http://hg.mozilla.org/labs/weave/rev/433ad50ee941
Set the record manager for CryptoMetas, PubKeys, PrivKeys after uploading keys.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.5
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: