On 19/02/13 09:25, Toni Alatalo wrote:
So this is “a module in core”, while R.Gunther thinks there’s “too much in core and not enough in modules”. So R.Gunther is happy as this is indeed a module? Even though it is in ‘core’. Or? Is there a name/term for the non-module parts of that ‘core’ BTW -- the Opensimulator Kernel or what? 😊 Core-Core? (I use that sometimes for Tundra core to differentiate from also-modules-in-central-repo/default-distro, which some others call ‘core’ similarily to opensim speech I think).
At this stage, many parts of OpenSimulator that are implemented modules as core to the project, such as inventory access modules and archiving modules.
Many, many years ago, a split was done in OpenSimulator to put things in 'CoreModules' and 'OptionalModules' with the intent of moving the optional modules out one distant day. However, I suspect some of those optional modules would now be properly considered core. Whether anybody actually ever removes the 'OptionalModules' DLL I don't know.
The line for a 'core' module is somewhat arbitrary since I think it depends on a number of factors, such as how much a particularly piece is infrastructure, how much use it would get, how many core developers are willing to maintain it, etc. And this may well evolve over time.
~Toni *From:* Justin Clark-Casey <[email protected] <mailto:[email protected]>> *Sent:* February 19, 2013 3:16 AM *To:* [email protected] <mailto:[email protected]> *Subject:* Re: [Opensim-dev] Diva Groups and Offline IM Yes, I think this is a perfectly reasonable kind of thing to go in core, as I would regard it as basic infrastructure. It will be a module in core anyway, and the existing external groups solutions (Flotsam and Simian, for example) will continue to work. I would also like to thank Diva for contributing this functionality - a core groups service is something I've wanted to see for a very long time but never had the time to implement. On 17/02/13 01:54, John Sheridan wrote: I'm just theorizing here, but I would think that common components required for interoperability between grids would need to go into the core. Just recently I finished writing my own offline IM handler in c# only to realize it didn't save messages that came in from over the hypergrid. I've yet to dig in to see why, but after pouring over different examples on how to get profiles working I'm quickly realizing that there is a need for a common way for all of these services to communicate. Its one thing to have your own proprietary communications formats if you're running a closed grid, but in the case where your components need to talk to other people's - that seems to be a different story. For example, with my profiles module I wanted to create a set of data objects (psProfile, psProfilePick, psProfileClassifieds, etc.), serialize them on the sim end, then ship them off to the profiles server and vice versa. After seeing how other projects out there communicate with their server counterparts, it became blatantly apparent that my way would work just fine if it were used on a closed grid but not in a Hypergridded environment where it would need to talk to countless other profile servers that all likely communicate in different ways. I'm pretty sure the same would hold true for offline messaging, groups, and so on. On 02/16/2013 07:32 PM, R.Gunther wrote: Opensim core ? I hope it's going to be a module, and not in the core of opensim. I have the idea there's already to much in core and not enough in modules. On 2013-02-16 21:07, Diva Canto wrote: Heads up: after discussion within core devs, the Groups and Offline IM addons I did for D2 are going to be donated to core opensim. This means that core opensim will have support for these out of the box without having to install any further components (i.e. apache). They work both for standalones and grids. Diva Groups has the optional HG service for supporting groups with foreign users. It also implements notices with attachments, something that is missing from Flotsam groups. It does not implement the voting and accounting features of the viewer (patches welcome). For those using Flotsam or Simian Groups, they're all mutually exclusive -- the config decides which one to use. The code will be added within the next week. If there are any issues or questions, let us know. Cheers Diva _________________________________________________ Opensim-dev mailing list [email protected] <mailto:[email protected]> https://lists.berlios.de/__mailman/listinfo/opensim-dev <https://lists.berlios.de/mailman/listinfo/opensim-dev> _________________________________________________ Opensim-dev mailing list [email protected] <mailto:[email protected]> https://lists.berlios.de/__mailman/listinfo/opensim-dev <https://lists.berlios.de/mailman/listinfo/opensim-dev> _________________________________________________ Opensim-dev mailing list [email protected] <mailto:[email protected]> https://lists.berlios.de/__mailman/listinfo/opensim-dev <https://lists.berlios.de/mailman/listinfo/opensim-dev> -- Justin Clark-Casey (justincc) OSVW Consulting http://justincc.org http://twitter.com/justincc _________________________________________________ Opensim-dev mailing list [email protected] <mailto:[email protected]> https://lists.berlios.de/__mailman/listinfo/opensim-dev <https://lists.berlios.de/mailman/listinfo/opensim-dev>
-- Justin Clark-Casey (justincc) OSVW Consulting http://justincc.org http://twitter.com/justincc _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
