Closed Bug 481741 Opened 16 years ago Closed 16 years ago

Switch to JSON from nsIJSON

Categories

(Cloud Services :: General, defect, P2)

Product:
Cloud Services
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

Details

We currently use Svc.Json.encode/decode which hits nsIJSON. Javascript natively supports JSON.stringify/parse and has less overhead than going through XPConnect. We might still want a wrapper to keep calls as encode/decode and call the right JSON instead of changing everything everywhere... but that's another source of overhead. Every time we encode, we'll need to grab Weave then Svc then Json then actually call. Just need to double check that we don't use the *FromStream methods: http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/json/nsIJSON.idl#49
Blocks: 468694
Priority: -- → P2
Target Milestone: -- → 0.3
Target Milestone: 0.3 → 0.4
No longer blocks: 468694
http://hg.mozilla.org/labs/weave/rev/b02155eb42aa Got rid of Svc.Json and various local nsIJSON instances.
Assignee: nobody → edilee
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.