use legacy connection what does it mean?

291 views
Skip to first unread message

Horst Schulze

unread,
Dec 4, 2018, 5:26:08 AM12/4/18
to MIT App Inventor Forum
Hi all,

the new companion gives a checkbox use legacy connecion. I Thought searching for that issue "use legacy connection" will give me an answer or a description in the companion help, but really nothing.
I mean a new issue like this could be documented. maybe under another title so that a search in the library may give a response. But nothing?

So:

What does it mean? Do I need it? Where to find details on it?

Horst

SteveJG

unread,
Dec 4, 2018, 9:12:05 AM12/4/18
to MIT App Inventor Forum
What does it mean?

The Companion's Legacy check box is described in the link on the App Inventor splash screen    Information about what has changed          

This feature relates to how App Inventor uses your browser. Since December 1, App Inventor does this differently than prior to that date.  The new connection method is called WebRTC "If WebRTC, the default approach in Companion version 2.48, doesn’t work on your network, you can switch back to the legacy approach by checking the (new to this release) “Use Legacy Connection” checkbox on the Companion’s main screen."       

Do I need it?   Probably not, you only need it if the default WebRTC does not work properly for you. If you connect to Companion OK, then just ignore this option; if you have a bad connection, try checking the box.   Most users will NOT need to do this.  Eventually, the check box will probably be removed as MIT gains experience with how users are able to use WebRTC successfully.

 Where to find details on it?        At the link above.

Regards,
Steve

Horst Schulze

unread,
Dec 9, 2018, 7:13:31 PM12/9/18
to MIT App Inventor Forum
ok. Thanks. I didn't found it on the release notes. Probably because I didn't read it.

And I didn't find it looking for "use legacy connection" ??-ok.

Horst

SteveJG

unread,
Dec 9, 2018, 7:20:54 PM12/9/18
to MIT App Inventor Forum

248Companion.png

MIT didn't provide a lot of information.  All it means is that if you check the box and then scanQR code, the Companion is supposed to be have just like before nb172 was posted.  When I do that, I see no difference.  The idea if the Companion has issues working without checking "Use Legacy Connectioin", the user should check the box and see if it makes a difference in how the connection behaves.    Legacy means  something that is carried over from an earlier time.  In this case, the type of connection used before MIT changed the connection to the WebRTC system.


Horst Schulze

unread,
Dec 10, 2018, 4:01:57 AM12/10/18
to MIT App Inventor Forum
>>MIT didn't provide a lot of information.
That's the problem. There seem to be a fondametal error in their teaching system. Making students and others searching for minor informations is wasting brain and presenting a non-user-oriented helpsheet teaches the students not to care for their customers.  In fact. MIT is known as hi level in research, so it can be low level in teaching. Students will come.
ok.
Thats going to a another issue. I understood - thanks to your help.

Horst

SteveJG

unread,
Dec 10, 2018, 8:26:03 AM12/10/18
to mitappinv...@googlegroups.com
The purpose of the Forum is to help others users when they are in trouble and need some advice or clarification of documentation or do not understand something.  No matter how competent one is in what is a foreign language, sometimes nuisances and unfamiliar words make it difficult.  The Forum exists to provide clarification for users.  You yourself have used the Forum 133 times to get advice.  That is great.  Keep asking.  When in doubt the student should ask for advice.

 The AI staff is small.  Would users prefer adequate documentation and few new features or extensive documentation and the status quo?   Google changed much of their policy in a very short time frame.  The wizards needed to come up with a different way for App Inventor to work to be in compliance with those policies. Fortunately they are doing that.  The developers do not change things to irritate the users.  The wizards do what must be done to continue to provide this FREE and incredibly useful educational compiler..  Not happy, there are other Android programming compilers.

Merry Christmas / Fröhliche Weihnachten and best wishes.

Horst Schulze

unread,
Dec 10, 2018, 11:53:44 AM12/10/18
to MIT App Inventor Forum
ok. Thanks.

Horst Schulze

unread,
Dec 11, 2018, 3:06:39 AM12/11/18
to MIT App Inventor Forum
If you have connections and a change could be made.My propositons in red

Release nb172 has been released

TL;DR

The MIT App ... difference:

  1. In ... below.)
  2. We have changed the way the MIT AI2 Companion connects to the browser. We anticipate that this change will work better in many situations. However, the newer method of connecting may not work with some network configurations.
  3. If this is the case, you will be able to instruct the Companion to use the older “use legacy connection" method, making it work as it did prior to this release.

Changes in Release nb172

One Buildserver for Google Play and All Devices!

We .. goes live).

companion.png

A New Way To Communicate (WebRTC)

The other significant---- chosen ports for communicating.


Use legacy connection -the old way to connect is still availlable

If WebRTC, the default approach in Companion version 2.48, doesn’t work on your network, you can switch back to the legacy approach by checking the (new to this release) “Use Legacy Connection” checkbox on the Companion’s main screen.

Please let us know if our new communications approach fails on your network. Eventually we will have to remove the legacy method in order to finally move MIT App Inventor to being delivered via https.


Thank you and Happy Inventing!

SteveJG

unread,
Dec 11, 2018, 8:23:40 AM12/11/18
to MIT App Inventor Forum
Your suggestion has been passed on to the MIT people who review documentation Horst.  You have included some good 'clarifications'.  Let's see whether the changes might be made before MIT issues another bug fix, perhaps later this month.

Thank you for your input.

-- Steve
Reply all
Reply to author
Forward
0 new messages