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

Daniel commented on CB-6661:
----------------------------

They will still have a 'native bridge' per se. If I understand the project's 
structure, the api calls by the plugins would basically all get converted to 
web requests in the platforms exec.js. Our 'native' code would be a new project 
 like apache/android that would handle all the requests.  In the case of 
something like 'Contacts' there won't be a real interface there. However, 
geolocation could tap into the servers IP and file storage would download files 
onto the server (this would remove the need for browser-local storage).  

The value is one code base, leveraging all the same functionality with adjusted 
look and feel. Also this would provide ways to rapid prototype without waiting 
for slow emulators. This would also give a simplified nightly build process and 
access to additional testing frameworks.

> Web Platform Target
> -------------------
>
>                 Key: CB-6661
>                 URL: https://issues.apache.org/jira/browse/CB-6661
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CordovaJS
>    Affects Versions: 3.4.0
>         Environment: All
>            Reporter: Daniel
>            Priority: Minor
>              Labels: cordova-js, features, platform
>             Fix For: 3.4.0
>
>
> I have not been able to find built in functionality for cordova to deploy an 
> app to a server platform. This purpose of this new platform is to allow an 
> HTML5 application within a Cordova project to be deployed on a web server, 
> available for access over standard internet protocols.
> My team and I will be actively working this at 
> https://github.com/CollinearGroup/cordova-js
> We intend to build this functionality with a nodejs server but hope that we 
> can provide the server with varying backends like Grails and Rails.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to