You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/10/08 05:51:16 UTC

[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1546: Implement a new SPI mechanism to replace Java native SPI mechanism

TeslaCN commented on issue #1546:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1546#issuecomment-705345807


   Personally I think that:
   1. Those implementations of interfaces are highly modular (such as 'elasticjob-error-handler-email'). Users just introduce the dependencies as needed.
   2. A certain implementation can be distinguished by a string based type defined in 'TypedSPI'. Iterator is acceptable because factory methods are invoke less frequently.
   3. The current factories using static block to institate instances.
   
   You may consider referencing the SPI registry in https://github.com/apache/shardingsphere.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org