> > Hmmm... Personally I'd be careful about not adding in too much > > stuff right now.
> Well, first of all when I say "built-in" I really meant it to be an > extension rather than in the core API, so if you don't want it, > that's ok. > > I think the idea of ensuring that the API is REST-friendly is > important though. 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. :-) 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. 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. Tough decision... Cheers, Dave _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
