Community
Participate
Working Groups
Snaps requires it's own documentation that should be packaged and distributed with Snaps. I propose the following table of contents. 1. Requirements (What version of Virgo will Snaps work with, (3+ and not Jetty) 2. Snaps concepts (Explain the theory of how it works, 3. Installing (Put bundles and plan in repo and add plan to initial artifact) 4. At a medium level show them how to develop a Snaps application. Referencing the menu bar sample. 5. Talk about the Snaps API and referencing the parent Servlet Context etc... 6. Conclusions (here are some other sample apps and some other things you can do e.g. styling bundles) I think this covers everything and gives a ruff idea about what should be going in. Some areas will need some good exploration, especially 5. Some features are not covered by samples apps either, may want to consider that.
Dmitry, could you look over this ruff table of contents and see if there is anything you think I missed.
I think documentation should go into some detail on how request is routed by the SnapFilter. Mention that only single level urls are supported currently. That is /foo/bar is not supported for the snap context prefix. Should also caution against tunneling into host servlet context, request attributes, session attributes as it might cause CCE or other worrisome issues with class-space consistency and versioning (host imports v=1.0.0 and snap 1.1.0 of some support package - and that class sits in the some sort of scope). In my mind snap should be as independent from host as possible and any communication between two (if required) should go through service registry. Host is mostly just an invisible pane around the snap vs. a root_web_app context (in spring terms).
Docbook project added in the snaps repo and integrated to the build.
Done and pushed to master
