List view
These are bugs known to exist and not planned to fix in 1.0.0, but may be fixed in response to patches or user requests.
No due date•0/4 issues closed- No due date•0/12 issues closed
Aim to have probed out any issues by building a solid sample application prior to moving on to release candidate
No due date•1/3 issues closedProvide the ability for 3rd parties to build plugins for things like Wordpress using a RESTful API. - Provide package and docs for running Atom server - REST port of Atom server capabilities - Authentication options - Provide REST server package with e.g. cloudfoundry deploy instr's - Provide ReST server as WAR with tomcat deploy instructions - Provide Jenkins style executable JAR (self-hosting webapp) - Provide as service available on Heroku - Provide docs, examples and blog articles (other RPM/Deb packaging with startup on specified port)
No due date•0/1 issues closedThe 1.0.0 release aims to be worthy of the attention of developers who wish to build applications which have previously been complex or not worth considering. The first two milestones focused on ease of development. Full feature set should include: (subject to resources...) - Supported disk persistence mechanism - probably TxLog + snapshots only (in memory) - Mapping strategy for mapping class fields to fuzzy attributes - Some good examples - A live site running on this (perhaps migrate fridgemountain.com)
Overdue by 13 year(s)•Due by February 28, 2012•4/7 issues closedNeed to look at requirements around removing Java serialization from the server format and creating a longer term persistence format which we can support through multiple releases. Here are some ideas for work to do: Data format: - Use MessagePack to encode data - and keep in this format at server end and on disk - Write scorers to work with MessagePack format - Perhaps even allow fields in a class to be scored by name...
No due date•0/4 issues closed