Backend API: need API to deal with transport storage from backend side about spectrum2

[piwats]

+1

[moyamo]

Do you propose a generic access to the backend database (i.e. can execute any query) or just access to existing spectrum tables?

[moyamo]

I don't think much changes are needed in spectrum for transwhat to work without a database. If after a user logs in, something similar to a handleBuddyChangedPayload (with all the Buddy fields filled in) is sent, transwhat should be able to get rid of the MySQL database.

[moyamo]

I still want to know what you have in mind. Will the Backend API allow plugins to create and manipulate tables or will it just allow you to query existing tables?

The problem is that just querying and modifying existing tables is not very useful. Spectrum already allows this through buddyChanged, updateBuddy and the like. If you allow the plugin to execute arbitrary SQL queries then the plugin has to worry about compatibility between the different databases. In this case the plugin might as well use the databases directly. If spectrum provides a high-level interface to the database then the type of queries the plugin can make will be limited.

So what will it be?

[jankaluza]

I've done the first part in commit ef1711d.

The backend can send following new option in backend config:

[features]
send_buddies_on_login = 1

And after that, Spectrum will send TYPE_BUDDIES protobuf message after the TYPE_LOGIN message including all the buddies from database.

[vitalyster]

Transwhat support is done in 2.0