SAP Cloud for Customer里Promise的实际应用场合是怎样的

魁首哥

作者

SAP Cloud for Customer里Promise的实际应用场合是怎样的

这篇文章将为大家详细讲解有关SAP Cloud for Customer里Promise的实际应用场合是怎样的，文章内容质量较高，因此小编分享给大家做个参考，希望大家阅读完这篇文章后对相关知识有一定的了解。

最近，我正在研究SAP Cloud for Customer的前端代码，我遇到了一个如何在那里使用promise的真实示例。下面是密码登录视图。

Once Passcode is entered, suppose I have already entered the system url and frontend user name in the past, they will be directly retrieved from browser storage.

Currently I use Chrome to access C4C and Web SQL is used as browser storage, where the system url and logon user name could be found from Chrome development tool.

The corresponding database initialization and table read is done by code below in file AppStatusService.js.

The series of callback functions are chained by promise API “then()” which are expected to be executed sequentially:

(1) _createTable() could only be executed after database initialization is done. (2) _getApplicationStatus could NOT be executed unless the database table which stores Application status is available – this is ensured by _createTable. (3) After application status is read from database table, _createDefaultEntries could be called to render the default value in Passcode logon view.

All above three steps are organized by promise to achieve the asynchronous execution mode. In order for me to understand how the above code works, I write a simplified version for illustration:

<!doctypehtml><html><head><script>varend;functionsetupDB(){returnthis.createDatabase().then(createTable).then(insertEntry).then(readEntry).then(printResult);}functioncreateTable(){returnnewPromise(function(resovle,reject){console.log("preparetocreatetable..."+Date.now());this._db.transaction(function(query){query.executeSql('createtableifnotexistsuser(idunique,user,passwd)');});setTimeout(_createTableOK.bind(this,resovle),1000);});}function_createTableOK(resovle){console.log("tablecreatedsuccessfully..."+Date.now());resovle();}functioncreateDatabase(){returnnewPromise(function(resovle,reject){console.log("preparetocreatedatabase..."+Date.now());this._db=openDatabase('mydb','1.0','JerryTestdb',1024);setTimeout(_createDatabaseOK.bind(this,resovle),1000);});}function_createDatabaseOK(resovle){console.log("databasecreatedsuccessfully..."+Date.now());resovle(this._db);}functioninsertEntry(){returnnewPromise(function(resolve,reject){this._db.transaction(function(query){query.executeSql("insertintouservalues(1,'Jerry','1234')");});setTimeout(_insertEntryOK.bind(this,resolve),1000);});}function_insertEntryOK(resolve){console.log("entryinsertedtotablesuccessfully..."+Date.now());resolve();}functionreadEntry(){returnnewPromise(function(resolve,reject){this._db.transaction(function(query){query.executeSql('select*fromuser',[],function(u,results){setTimeout(_readEntryOK.bind(this,resolve,results),1000);});//endofquery.executeSql}//endoffunction(query));//endofthis._db.transaction});}function_readEntryOK(resolve,oResult){console.log("entryreadedfromDBsuccessfully..."+Date.now());resolve(oResult);}functionprintResult(oResults){for(vari=0;i<oResults.rows.length;i++){document.writeln('id:'+oResults.rows[i].id);document.writeln('user:'+oResults.rows[i].user);document.writeln('passwd:'+oResults.rows[i].passwd);}end=true;}functionwork(){if(end){clearInterval(handle);}else{console.log("working..."+Date.now());}}setupDB();varhandle=setInterval(work,200);</script></head></html>

Open the html page with Chrome, and you can find that a database with name mydb and a table user is created with one record inserted.

In order to achieve the simulation that each step of webSQL is a time-consuming operation, I wrap the real logic into setTimeout with a certain time delay.

I scheduled function work to simulate the main work to do and the database related job are done in an asynchronous way organized within function module setupDB() by promise API.

The console output proves that the database operations are really executed asynchronously in exactly the same order as they are scheduled via then API of promise.