Hi, at this time, I believe the interfaces might grow, but are unlikely to change existing methods.
Two methods on the inventory interface are slated to be dropped, and already marked obsolete. Everything else can be considered more stable than anything we used to have. Melanie [email protected] wrote: > Mic Bowman wrote: >> In this case, one of the barriers we feel to productive public >> discussion (and probably documentation) about long-term, stable >> interfaces is a lack of belief that the discussion will matter in a >> substantial way to what gets coded. That is, if we went off & built the >> php/apache interfaces, we would have no influence over changes in the >> core & would therefore be completely subject to any decisions core >> makes. (Feels like taxation without representation or something like >> that... :-) >> >> So... You say that we can go off & build what we want... but that's only >> cost-effective if we fork or freeze (or wait)... > > Well, that's not exactly true that you don't have a say, since 2 core > devs are your employees :) > > But wrt to stabilization, as I said, those interfaces are the main > contract. Notice that these interfaces didn't exist, as such, before. > Now they do. Before now, no one here could point to a piece of the code > base and tell you "hey, here's the contract". Now we can. I'm hoping > that, after some minor clean-ups (exception: IInventoryService needs a > major cleanup) those interfaces will freeze. I'd be very surprised if > those interfaces will go through major changes after 0.7. That's my word > only, I don't speak for the entire project, but, really, I'd be *very* > surprised. > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev > > _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
