Short URI payload-status systems and methods
A short URI, provided by a server on behalf of a third party, may be evaluated by selecting a device agent associated with the short URI and determining a destination URI corresponding to the device agent and the short URI, the destination URI identifying a payload. The server requests the payload and determines a current payload status by evaluating characteristics of the response against response characteristics that are expected based at least in part on a payload type of the payload. A payload status report is provided to the third party indicating the determined current payload status.
1. A server-implemented method of evaluating short URIs provided by the server on behalf of a third party, the method comprising:
selecting, by the server from a multiplicity of short URIs provided by the server, a plurality of short URIs provided on behalf of the third party;
for each of said plurality of short URIs:
selecting, by the server, at least one device agent associated with the current short URI from a plurality of device agents;
obtaining, by the server, a destination URI corresponding to said short URI and said at least one device agent, said destination URI identifying a payload associated with said at least one device agent;
sending a request for said payload;
determining, by the server, one or more expected response characteristics associated with said request based at least in part on a payload type of said payload; and
determining, by the server, a current payload status associated with said short URI and said at least one device agent based at least in part on evaluating one or more actual response characteristics corresponding to said request according to said one or more expected response characteristics; and
providing, by the server, a payload status report to the third party indicating said determined current payload statuses associated with said plurality of short URIs.
2. The method of claim 1 , wherein said at least one selected device agent comprises a mobile-device web-browser user agent.
3. The method of claim 2 , wherein sending said request for said payload comprises spoofing said mobile-device web-browser user agent.
4. The method of claim 1 , wherein said at least one selected device agent comprises a mobile-device application.
5. The method of claim 4 , wherein sending said request for said payload comprises the server mimicking a series of network communications as if said mobile-device application were communicating with a remote server hosting said payload.
6. The method of claim 4 , wherein sending said request for said payload comprises the server executing a copy of said mobile-device application within an emulated mobile-device operating environment.
7. The method of claim 4 , wherein sending said request for said payload comprises instructing a mobile device controlled by the server to request said payload via said mobile-device application executing on said mobile device.
8. The method of claim 1 , further comprising retrieving said payload.
9. The method of claim 8 , wherein determining said current payload status comprises comparing at least a portion of said payload to a corresponding portion of a previously retrieved payload associated with said destination URI.
10. The method of claim 8 , further comprising storing at least said portion of said payload for comparison with a subsequently retrieved payload associated with said destination URI.
11. The method of claim 9 , wherein said payload comprises a document comprising machine-readable markup.
12. The method of claim 11 , wherein comparing at least said portion of said payload to said corresponding portion of said previously retrieved payload comprises building a payload document object model according to said machine-readable markup.
13. The method of claim 12 , wherein comparing at least said portion of said payload to said corresponding portion of said previously retrieved payload further comprises comparing one or more elements within said payload document object model to one or more corresponding elements associated with said previously retrieved payload.
14. The method of claim 1 , further comprising the server automatically submitting said evaluation of said one or more actual response characteristics to a human evaluator when said one or more actual response characteristics cannot be automatically determined to match or not match said one or more expected response characteristics.
15. The method of claim 14 , wherein automatically submitting said evaluation of said one or more actual response characteristics to a human evaluator comprises crowdsourcing said evaluation of said one or more actual response characteristics to an undetermined one of a plurality of remote human evaluators.
16. The method of claim 14 , further comprising receiving an evaluation response from said human evaluator and automatically updating said payload status report according to said evaluation response.
17. The method of claim 1 , wherein said payload status report further comprises a plurality of images into which said plurality of short URIs have been respectively encoded as machine-scannable codes.
18. The method of claim 1 , wherein said payload comprises data according to which a mobile device may obtain a mobile-device-executable application.
19. The method of claim 18 , wherein said one or more expected response characteristics comprise at least one of an application-cost characteristic, an application-version characteristic, an application-title characteristic, an application-requirements characteristic, an application-title characteristic, and an application-description characteristic.
20. A non-transient computer-readable storage medium having stored thereon instructions that, when executed by a processor, configure the processor to perform the method of claim 1 .
21. A computing apparatus comprising a processor and a memory having stored thereon instructions that, when executed by the processor, configure the apparatus to perform the method of claim 1 .