Hi devs,
I've created a small tutorial to integrate Angular 2 application with
Apache Cordova. I wonder if it could be useful for the community and in
that case here is the link so you can refer to it in case that you found it
useful.
The patch and pull request are ready since one week ago. The patch handles
the 304 status code for android adding a new error status code, I've also
updated the documentation and the mobile spec tests. Shall I do something
more? TIA.
just to save an extra
request that it's not necessary. Using different request means that in the
worst case, I will have to do two request per resource to update.
Ian
On Tue, Jun 17, 2014 at 11:56 AM, Javier Puerto jpue...@gmail.com
wrote:
I think it's better to use the error callback
will add also the documentation for the new
caching status code and open a new pull request.
On Mon, Jun 16, 2014 at 5:39 AM, Javier Puerto jav...@apache.org wrote:
Hi Cordova developers,
I'm creating a system to download/update several resources from a server
to
the device and I've
at 4:18 AM, Javier Puerto jpue...@gmail.com wrote:
2014-06-16 17:01 GMT+02:00 Andrew Grieve agri...@chromium.org:
I think this behaviour has been around for a while, and makes sense in
the
majority of cases.
Yep, I did a git blame and this fragment of code was there from
, success nor error callbacks. In the issue comments there's a deep
explanation and the complete test attached.
Does anyone experienced this issue before? the method is supposed to work
and indeed it's working with the patched file-transfer plugin. A new bug?
2014-06-12 11:08 GMT+02:00 Javier
Hi Cordova developers,
I'm creating a system to download/update several resources from a server to
the device and I've observe a behaviour that breaks my use case.
After fix the issue CB-6928, I'm able to download/update all the resources
without problems. My next test was to try to download the
Hi all cordova developers,
I'm working on a project based on the Apache Cordova framework. Using the
file-transfer plugin I've noticed that the behaviour for HTTP cached
resources is not correct. I've opened an issue explaining the problem
https://issues.apache.org/jira/browse/CB-6928
I've also
