A few days ago, I was discussing the issue of jwfd with a friend. He made a good suggestion that jwfd should enhance the encapsulation of functions at the process operation level, it also provides a set of interfaces that are easy for users to call. This suggestion immediately aroused my resonance as I did this design in the past, for example, the SQL operation function of the process database is encapsulated into a class and instructions are written for these classes. However, it seems that this is far from enough, providing a complete set of flow operation control function interfaces for friends should be another important task of the worker FD in addition to adding new functions. Simply put, it is necessary to form an SDK package for the worker FD, A set of callable jar libraries are provided for external users. After drawing the flowchart and submitting it to the database, users can call the functions in the SDK without writing them.CodeTo control the operation of the process ......
Encapsulate the process control functions, add the interrupt mode and event mechanism (review the computer composition principle and think the interrupt mechanism is very useful), and combine the bus-based adaptive transformation project of arc, form a new generation of worker FD workflow engine core architecture ..... Thanks to my friends for your advice, a little bit of tips can bring me a lot of new inspiration .....
I recently fell in love with a game called warships (warship) and 3vs3 in Starcraft 2. Let's play on the network... It's really fun... The trick of this game is to deploy a certain number of weapons and equipment on a limited warship space, so that the warship has the strongest firepower or defensive power. This is a great deal of fun... It is very helpful for training system thinking...