David Leangen wrote: > Yep. Personally I agree with you. Lately I've really bought into the REST > principle and I'm in the process of updating my apps to be RESTful. I'm just > wondering where this will stop in terms of Qi4j dev... Could we not just get > the core into production first before we think about adding extensions? > > I'd really like to get going with something now and have my appetite whet > for extensions later than having to wait another year to start at all. :-)
Right, well the core of API will be released shortly (and in fact there is already an 0.1.0 release in the Maven repo, we just aren't talking about it for various reasons). The REST extension would to start with just be to make sure we don't have any unnecessary limitations in core that makes it impossible. > Anyway, I know that the design is the fun part. Who wants to do marketing. > Bleh. But the faster we get out a working core, the faster we'll start to > make converts. Agree. And we also need to validate that the whole thing works at all :-) > But then again, by being more thoughtful about things now, I guess the > chances of getting things right are better. If we decide later as an > afterthought to, for example, add REST, maybe we'll notice (too late) that > it's not so easy. Well, as above, for now I am mostly interested in making some basic tests to make sure that the core API is RESTifiable. There's tons of stuff that is possible to do with a full implementation, but that doesn't have to be done today (and certainly not by myself either, as I am a complete REST-newbie). /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
