Hi Sarwar,
at this moment there is one functionality that I need to add on the
server side, pulling periodically from email accounts. Everything else
will be done in the client, Sling will do persistence.
What I meant was whether or not my sling client should use the JSON I
get from query results in order to build the node tree or should I
preferably use XML results.
Günther
Am 13.05.12 11:48, schrieb Sarwar Bhuiyan:
You can write sling servlets or jsps that return data in whatever format is
configurable for you. Are you planning on adding any bundles to sling or
doing the entire thing in the client?
Sarwar
On 13 May 2012 05:29, "Günther Schmidt"<[email protected]> wrote:
Hi everyone,
I'm planning quite an ambitious project, a swing desktop app (based on
Netbeans Platform) which is supposed to offer Groupware functionality& DMS.
In particular the app will eventually include
* an email client
* a task module
* a calendar module
* manage binary files
* and whatever else I can think of and add it later
I have chosen Apache Sling as the backend because of its REST API, I just
didn't care for RMI access as I might need WAN access to the backend so
HTTP / REST should make this easier. Another thing why I chose Sling is
because of the OSGi based architecture, one of its tasks will be to
periodically pull in new email from IMAP / POP3 servers.
Now, to get started, with the client, I'll try to implement a JCR browser.
I know that I can query the Sling repository and get JSON back, is this
the most feasible format or should I rather try to get XML results?
Günther
