Apache OFBiz User Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 12.3.4. Performance Management and Employee Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 12.4.5. Performance Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cache will load all products and product categories into the cache; this is good for improved application performance. only basic product and category information from the first Product and Category0 码力 | 307 页 | 5.64 MB | 1 年前3
Apache OFBiz User Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 12.3.4. Performance Management and Employee Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 12.4.5. Performance Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cache will load all products and product categories into the cache; this is good for improved application performance. only basic product and category information from the first Product and Category0 码力 | 304 页 | 5.21 MB | 1 年前3
Apache OFBiz Developer Manualpossibly in production on different domains. This can happen for different reasons, most often for performance reason. As it’s annoying to give each time a credential when changing from an OFBiz application to transmit to renderer all screen elements and if there was "use-when" for manage them in the frontend. This way next call could sent "use-when" correct value to properly update the final screen. 49 92 We currently use JWT in 2 places: 1. To let users safely recreate passwords (in backend and frontend) 2. To allow SSO (Single Sign-on) jumpings from an OFBiz instance to another on another domain0 码力 | 108 页 | 2.47 MB | 1 年前3
Apache OFBiz Developer Manualpossibly in production on different domains. This can happen for different reasons, most often for performance reason. As it’s annoying to give each time a credential when changing from an OFBiz application to transmit to renderer all screen elements and if there was "use-when" for manage them in the frontend. This way next call could sent "use-when" correct value to properly update the final screen. 49 92 We currently use JWT in 2 places: 1. To let users safely recreate passwords (in backend and frontend) 2. To allow SSO (Single Sign-on) jumpings from an OFBiz instance to another on another domain0 码力 | 108 页 | 2.47 MB | 1 年前3
Apache OFBiz Developer Manual Release 18.12possibly in production on different domains. This can happen for different reasons, most often for performance reason. As it’s annoying to give each time a credential when changing from an OFBiz application claims. We currently use JWT in 2 places: 1. To let users safely recreate passwords (in backend and frontend) 2. To allow SSO (Single Sign-on) jumpings from an OFBiz instance to another on another domain0 码力 | 53 页 | 1.52 MB | 1 年前3
Apache OFBiz Developer Manualpossibly in production on different domains. This can happen for different reasons, most often for performance reason. As it’s annoying to give each time a credential when changing from an OFBiz application claims. We currently use JWT in 2 places: 1. To let users safely recreate passwords (in backend and frontend) 2. To allow SSO (Single Sign-on) jumpings from an OFBiz instance to another on another domain0 码力 | 65 页 | 1.22 MB | 1 年前3
Apache OFBiz Developer Manual Version trunkpossibly in production on different domains. This can happen for different reasons, most often for performance reason. As it’s annoying to give each time a credential when changing from an OFBiz application 65 We currently use JWT in 2 places: 1. To let users safely recreate passwords (in backend and frontend) 2. To allow SSO (Single Sign-on) jumpings from an OFBiz instance to another on another domain0 码力 | 81 页 | 1.77 MB | 1 年前3
2021 中国开源年度报告open source community. However, it is not the primary consideration, and only when the product performance is not much different will they choose the vendor who contributes to the open source community that contributes a lot to the open source community when there is little difference in product performance. 【专家点评】/ [Expert Comment] 姜宁:这里的开源产品是指基于开源项目的商业化产品吧!大部分的情况下,开源项目的 选型是由在一线的开发人员决定的,但是由于公司决策链的关系,商业产品的购买还是要 is still at the top of the list with a very high level of activity, and we expect even better performance in the future. 【专家点评】 二、 中国活跃度排名 Top30 China Activity Ranking Top30 repo_name0 码力 | 199 页 | 9.63 MB | 1 年前3
Apache OFBiz User Manual Version trunk Version unspecified. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 13.2.4. Performance Management and Employee Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 13.3.5. Performance Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cache will load all products and product categories into the cache; this is good for improved application performance. only basic product and category information from the first Product and Category0 码力 | 237 页 | 2.74 MB | 1 年前3
Inkscape Beginners’ Guide 1.1This guide is a living document. This means that it is actively being edited and continuously being improved—and you can contribute! If you find something that is confusing, wrong, or otherwise needs to be Desktop Cutting Plotter (AutoCAD DXF R 14) (*.dxf) plotter file format Enhanced Metafile (*.emf) improved version of .wmf with support for Bézier curves Encapsulated PostScript (*.eps) embeddable printer Visio Microsoft Visio Diagram (*.vsd) diagrams created in MS Visio Windows Metafiles (*.wmf) improved version of .wmf with support for Bézier curves WordPerfect Graphics (*.wpg) graphics exported0 码力 | 241 页 | 14.61 MB | 1 年前3
共 25 条
- 1
- 2
- 3













