Return-Path: 
 <issues-return-8615-apmail-cordova-issues-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org
Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8C9E2106ED
	for <apmail-cordova-issues-archive@minotaur.apache.org>;
 Tue,  9 Jul 2013 17:35:49 +0000 (UTC)
Received: (qmail 74389 invoked by uid 500); 9 Jul 2013 17:35:49 -0000
Delivered-To: apmail-cordova-issues-archive@cordova.apache.org
Received: (qmail 74357 invoked by uid 500); 9 Jul 2013 17:35:49 -0000
Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cordova.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cordova.apache.org>
List-Post: <mailto:issues@cordova.apache.org>
List-Id: <issues.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list issues@cordova.apache.org
Received: (qmail 74343 invoked by uid 99); 9 Jul 2013 17:35:49 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 17:35:49 +0000
Date: Tue, 9 Jul 2013 17:35:49 +0000 (UTC)
From: "Joe Bowser (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12647424.1368493095644.19772.1373391349106@arcas>
In-Reply-To: <JIRA.12647424.1368493095644@arcas>
References: <JIRA.12647424.1368493095644@arcas>
Subject: [jira] [Commented] (CB-3384) Resource Loading API for Android
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CB-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703538#comment-13703538 ] 

Joe Bowser commented on CB-3384:
--------------------------------

This should be good to go, right?  It passes the tests on this end.
                
> Resource Loading API for Android
> --------------------------------
>
>                 Key: CB-3384
>                 URL: https://issues.apache.org/jira/browse/CB-3384
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Android
>            Reporter: Andrew Grieve
>            Assignee: Braden Shepherdson
>             Fix For: 3.0.0
>
>
> Motivations:
> 1. Many plugins do not handle URLs correctly when they are in the form content: or file:///android_asset. 
> 2. For the cordova-app-harness, there needs to be a way to re-route resource load requests so that the harness can load app resources while still respecting the <content> tag.
> Short Description
> All plugins can watch the loading of any uri's Eg: opening of files, the browser making requests to load files etc etc.
> In addition to watching they may assist in loading the uri's.
> For example, a use case here is - suppose a mimetype for a hypothetical extension ".abc" doesn't exist, a plugin could check the extension of a loaded uri and set the mimetype. This would now be set for all files loaded in the system.
> Pseudo code of the mechanism:
> 1. make a request 'R' to a uri.
> 2. loop through all plugins to see if any plugins change the request
> 3. if the request changes, set 'R' to this modified request and repeat step 3
> 4. load request 'R' and return result

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira