Jeff, Here are the resources I mentioned in the call. https://build.allseenalliance.org/ci/view/Core%20RB16.04%20SDK/ contains all of the SDKs https://build.allseenalliance.org/ci/view/Core%20RB16.04%20SDK/job/branch-osx-sdk/ is the OSX SDK https://build.allseenalliance.org/ci/view/Core%20RB16.04%20SDK/job/branch-osx-sdk/configure-readonly/ shows the build steps Ry
On Thu, Jun 30, 2016 at 9:21 AM, Blayney, Jeff <[email protected]> wrote: > Way, > > > > We are currently pursuing your recommendation of using the new alljoyn > 16.04 router in windows 10. We will let you know what happens. > > > > Lioy, > > > > I have a meeting conflict, however our android developer Jon Mozzetta will > attend to answer any questions about these bugs that we are seeing. As a > short answer to your inquiry – we were seeing the multipoint issue (bug > #49) in the scenario outlined in the bug itself. It is around the network > disconnect/connect scenario – our program would never recover due to this > bug. > > > > https://jira.allseenalliance.org/browse/ASACORE-49 > > > > https://jira.allseenalliance.org/browse/ASACORE-3053 - (new bug logged > for leaveHostedSession issue on non-multipoint) > > > > Thanks, > > > > -Jeff > > > > > > *From:* Way Vadhanasin [mailto:[email protected]] > *Sent:* Wednesday, June 29, 2016 11:43 PM > *To:* Lioy, Marcello <[email protected]>; Blayney, Jeff < > [email protected]>; [email protected] > *Cc:* Poole, Gary <[email protected]>; Cazier, Robb P (CEPS SW > Development) <[email protected]>; Mozzetta, Jonathan < > [email protected]>; Truong, Binh <[email protected]> > *Subject:* RE: [Allseen-core] Multipoint Re-joining bug > > > > Hello Jeff, > > > > I’d like to learn more the issue(s) you're having in non-muiltipoint > configuration, specifically after your switch to more recent windows 10 > build in the Windows 10 Insider program. These recent Windows 10 builds > have the AllJoyn router based on the 16.04 release, which received a number > of fixes notably related to router deadlocks and the ECDHE_SPEKE > authentication mechanism (the ones you are currently using unfortunately > are in the deprecation path). > > > > Also as I recommended previously, please consider using the asynchronous > version of the session API (particularly when joining a session). It worked > much better in out testing. > > > > Thanks, > > Way > > > > > > *From: *Lioy, Marcello <[email protected]> > *Sent: *Wednesday, June 29, 2016 3:58 PM > *To: *Blayney, Jeff <[email protected]>; > [email protected] > *Cc: *Poole, Gary <[email protected]>; Cazier, Robb P (CEPS SW > Development) <[email protected]>; Mozzetta, Jonathan > <[email protected]>; Truong, Binh <[email protected]> > *Subject: *Re: [Allseen-core] Multipoint Re-joining bug > > > > Jeff, > > > > As I mentioned on Slack it would be great if you could join the triage > meeting tomorrow and explain what you are doing and how this impacts you > that will help make the case for fixing the issue. The trick will be to > find someone that can make the fix. > > > > *From:* [email protected] [ > mailto:[email protected] > <[email protected]>] *On Behalf Of *Blayney, > Jeff > *Sent:* Wednesday, June 29, 2016 3:05 PM > *To:* [email protected] > *Cc:* Poole, Gary <[email protected]>; Cazier, Robb P (CEPS SW > Development) <[email protected]>; Mozzetta, Jonathan < > [email protected]>; Truong, Binh <[email protected]> > *Subject:* [Allseen-core] Multipoint Re-joining bug > > > > Hello, > > > > I was hoping to lobby a higher priority for the bug listed below. We > intermittently could not rejoin a multipoint session, and this broke our > application for these cases with no simple workaround. We have since > switched to non-multipoint as a workaround, however that has its own unique > issues and challenges. We would like to be able to go back to multipoint at > some point. > > > > > https://jira.allseenalliance.org/browse/ASACORE-49?jql=project%20%3D%20%22Core%20SW%22%20AND%20(component%20in%20(%22Router%2FSCL%22%2C%20SCONS)%20OR%20component%20is%20EMPTY)%20AND%20(status%20%3D%20closed%20AND%20resolution%20%3D%20Postponed%20OR%20status%20not%20in%20(closed%2C%20resolved)%20AND%20issuetype%20%3D%20Bug)%20ORDER%20BY%20Severity%20DESC%2C%20priority%20DESC%2C%20id%20ASC > > > > Thanks! > > > > -Jeff > > _______________________________________________ > Allseen-core mailing list > [email protected] > https://lists.allseenalliance.org/mailman/listinfo/allseen-core > >
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
