You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/10/10 18:23:26 UTC
[jira] Commented: (DERBY-1936) Create sample application that
demonstrates Derby running offline in browser and synchronizing with
backend
[ http://issues.apache.org/jira/browse/DERBY-1936?page=comments#action_12441187 ]
Daniel John Debrunner commented on DERBY-1936:
----------------------------------------------
Just for the record this application depends on two third party downloads (and I assume is is coded against those apis):
1.7 GOOGLE CALENDAR DATA API JAVA CLIENT
http://code.google.com/apis/gdata/download/gdata.java.zip
http://code.google.com/apis/gdata/calendar.html
Licence is ALv2, see COPYING file in downloaded archive
1.8 JSON FOR JAVA
http://www.json.org/java/json.zip
Licence is in http://www.json.org/license.html
I think the licence is BSD-like, so I see no issues in having code in Derby's SVN that works against JSON APIs.
I don't believe we could have the JSON jar itself in the Derby achives since it does impose a restriction
on its use, "The Software shall be used for Good, not Evil.".
Thanks for the contribution David.
> Create sample application that demonstrates Derby running offline in browser and synchronizing with backend
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1936
> URL: http://issues.apache.org/jira/browse/DERBY-1936
> Project: Derby
> Issue Type: New Feature
> Components: Demos/Scripts
> Reporter: David Van Couvering
> Assigned To: David Van Couvering
> Priority: Minor
> Fix For: 10.2.2.0
>
> Attachments: localcal.diff
>
>
> This is a placeholder for the LocalCalendar application I have written which demonstrates the embedded/offline capabilities of Derby through a
> sample application that lets you manage GoogleCalendar events offline and synchronize when you come back online
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira