Project:
| View Revisions: Issue #34807 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0034807: [API change] Remove the trigger state field from mobile server definition as the server type (main) provides enough information | ||
| Revision | 2016-12-22 10:38 by mtaal | ||
| Description | The trigger state field (of the Mobile Server Definition table) flag was intended to define that a server's unavailability would trigger going offline or online. However in practice the server type is enough. All the relevant code already uses the utility method [1] checking both the servertype and trigger state. The idea was to support that new server types could trigger offline. But this should be re-implemented whenever this becomes relevant as we then have better knowledge on how it will be used. Also there is already some extension possible for offline checking [2]. [1] https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/ef3722f7a2bd/src/org/openbravo/mobile/core/servercontroller/MobileServerUtils.java#l41 [^] [2] http://wiki.openbravo.com/wiki/How_to_implement_custom_offline_checking [^] |
||
| Revision | 2016-12-22 10:35 by mtaal | ||
| Description | The trigger state field (of the Mobile Server Definition table) flag was intended to define that a server's unavailability would trigger going offline or online. However in practice the server type is enough. All the relevant code already uses the utility method [1] checking both the servertype and trigger state. [1] https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/ef3722f7a2bd/src/org/openbravo/mobile/core/servercontroller/MobileServerUtils.java#l41 [^] |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |