Closed Bug 704241 Opened 13 years ago Closed 13 years ago

Create "strict" mode for appsync server

Categories

(Web Apps Graveyard :: AppsInTheCloud, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: ianbicking, Unassigned)

Details

(Whiteboard: server [nonmwcblocker])

There are quite a few checks we can run on the appsync server that can verify the request. These may be inefficient, or may be too future-hostile to changes in sync, but right now I believe they would be useful. We need a couple parts: * Establish a configuration flag that we can use anywhere in the code * Set up a way to communicate this information back to clients, including non-fatal information (e.g., warning headers) * Put in some real testing code * Potentially deploy webtestrecorder around staging and dev, so if anyone detects a problem we can replay it exactly (watch out for disk space exhaustion!)
Priority: -- → P3
Whiteboard: server
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/24808871
Whiteboard: server → server [nonmwcblocker]
The old app sync codebase is no longer going to be supported. Apps in the cloud will be under a different codebase. None of these bugs are valid anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: Web Apps → Web Apps Graveyard
You need to log in before you can comment on or make changes to this bug.