[
https://issues.apache.org/jira/browse/COR-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282638#comment-14282638
]
Dennis E. Hamilton commented on COR-11:
---------------------------------------
What's the unit of interaction? Is there basically a single GET for the HTML
or is there something a bit more interactive running in the browser, and
something more interactive running on the server.
For example, could node.js be used for this? This might also make for a way to
use browsers on an off-line client too since it is an alternative to running a
web server, but it does have more footprint on the client. I don't know how
larger footprint can be avoided on a client-side case, and now with node or an
installable equivalent we now have more seems for configuring rich internet
applications to boot.
This does mean we would be talking about native code integration wherever the
"server" side of this is installed. We know that's doable, although more
involved in terms of deployment to multiple platforms and configurations.
Would this be a deployment case that can be seen as an implementation under the
overall architectural model for Corinthia viewing and editing functions?
> Make interface between docformat and webkit (prepare for e.g. Qt).
> ------------------------------------------------------------------
>
> Key: COR-11
> URL: https://issues.apache.org/jira/browse/COR-11
> Project: Corinthia
> Issue Type: New Feature
> Components: DocFormats - API
> Environment: source
> Reporter: jan iversen
> Priority: Blocker
> Fix For: 0.5
>
>
> We need a API to the library
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
