I am not sure why this question is even relevant to the OBS downtimes and packaging. Removing other mailing lists and keeping only meego-dev and changing the subject.
MeeGo supports d-bus as the de-facto IPC mechanism, but since most of the projects are upstream, they might choose to use their own IPC mechanism. -- Sateesh On Mon, Aug 22, 2011 at 11:27 AM, Manju_Reddy <[email protected]>wrote: > Hi all, I need some information on MeeGo please help in getting the > information. > > 1. what are all the IPC mechanisms MeeGo supports > 2. is there any custome IPC mechanism supported by MeeGo. > 3. does all the MeeGo IPC are POSIX's complaint. > > please i badly need this information please help me.. > > thanks > manju > > On 22 August 2011 11:21, <[email protected]> wrote: > >> Good moaning, >> >> It looks like core OBS has serious stability issues with its API service. >> This seems to have been masked by the http downtimes so far. There are still >> frequent, albeit mostly shorter, downtimes of the whole OBS as seen over >> http(s), but the major problem as seen from linked OBS perspective is that >> the API remains inaccessible after such downtimes. >> >> Core OBS has been in such a state now since: "Sat Aug 20 04:02:56 UTC >> 2011". >> The overall downtime for the last 7 days probably exceeds 3 days. >> >> I have now filed bug 22702 ( https://bugs.meego.com/show_bug.cgi?id=22702). >> >> Cheers >> >> Thomas >> >> PS: It took me a bit to find the right mailing list for this. >> ReleaseEngineering officially names meego-releases as primary contact, but >> according to the info blurb: “Anyone can subscribe to the list, but posting >> is moderated and limited only to people who publish MeeGo release >> information. For open discussion about anything posted here, you can take >> those discussions to meego-dev or meego-packaging as appropriate.” In the >> end I went with meego-packaging as that is explicitly named on >> http://build.meego.com/ “Please join our mailing list [...] for >> discussions around the Build Service.” >> I’ve CC’d meego-dev and meego-community as the impact for community OBS is >> high and issues have been discussed on both previously, post FOLLOW-UPS to >> meego-packaging though, please! I've also CC'd Adam as he is the only person >> who visibly said they would work on the previous OBS issue. >> _______________________________________________ >> MeeGo-community mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-community >> >> http://wiki.meego.com/Mailing_list_guidelines >> > > > _______________________________________________ > MeeGo-community mailing list > [email protected] > http://lists.meego.com/listinfo/meego-community > http://wiki.meego.com/Mailing_list_guidelines >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
