Allthough the user integration through MW Authplugin and automatic acount creation in MW if not existant seems to be the most professional solution. There is a miner drowback of how to handle change of preferences and logout situations.
some thoughts about unsolved problems - Preferences such as email do exist and are stored twice the vB and MW and should be changed in vB by user and then be updated in MW automaticly
- Logout should be made global which means that logout manualy in either vB or MW should log out both automaticly to be secure
- or even better the login in MW should just use the db of vB but not the login procedure then there could serveral MW installations eg german and english been run together useing the centralised vB User Data
The above thougts are not critic but merely helpless nonprogrammer effort to contribute on the grounds of checking possible cases.
shortes way by logic with smalles chance of interference
I do hope that in the end there can be achived a working bridge that does as little as possible except checking user data in the vB Database and producing doubles in MW in order to make things independent. The Preferences which exist twise should be changed in vB because of code copyright bull++++ and then updated in MW automaticaly where only Preferences should be changeble which are nonexistant in vB.
I hope my thoughts might trigger some genius programmers efforts to solve the problem with minimum effort.
Sincerely yours
Burgy Zapp with greatings from Hagenheim