reader | Web阅读器服务端

Rather than using two different function, one for adding card image and one for card content, try combining both of them.. here use the code for your reference.

To compare, you first need to put your condition inside while (reader.Read()){} . then add the column number of your table to reader[].toString() in your if-else condition. learn more about Database adapters before you do these!

You have not specified which platform you're on!

Have a go with this

We need /u to handle unicode and then .+ instead of \w because of the double bytes

More stuff using Unicode regex

Regular expression \p{L} and \p{N}

JdbcCursorItemReader uses a JDBC cursor (java.sql.ResultSet) to stream results from the database and is not thread-safe.

JdbcPagingItemReader reads items in pages of a configurable size and is thread-safe.

Instead of taking it in JSONObject, parse it in JSONArray.

You don't need to use .split()

This is because your ItemProcessorSurveillance implements two interfaces: ItemProcessor and StepExecutionListener but is only registered as an ItemProcessor in the step. It should also be registered as a listener so that beforeStep is called when appropriate to set the stepExecution field.

Ok, the signature container is embedded correctly.

But there are issues with the signature container itself:

• Both in the SignedData.digestAlgorithms collection and in the SignerInfo.digestAlgorithm value you have used the OID of SHA1withRSA, but that is a full signature algorithm, not the mere digest algorithm SHA1 expected there.

• Then the SHA1 hash of the signed bytes is BB78A402F7A537A34D6892B83881266501A691A8 but the hash you signed is 90E28B8A0D8E48691DAFE2BA10A4761FFFDCCD3D. This might be because you hash buffer2 and

  buffer2 has empty contents data (/Contents <>)

  The hex string delimiters '<' and '>' also belong to the contents value and, therefore, must also be removed in buffer2.

Furthermore, your signature is very weak:

• It uses SHA1 as hash algorithm. SHA1 meanwhile has been recognized as too weak a hash algorithm for document signatures.
• It doesn't use signed attributes, neither the ESS signing certificate nor the algorithm identifier protection attribute. Many validation policies require such special attributes.

1. It is the main method, so there is no need to cleanup. When main returns, the program exits. If this wasn't the main, then you would be correct.

2. There is no best practice that fits all use cases. The code you show here is a very common pattern. The function creates a goroutine, and returns a channel so that others can communicate with that goroutine. There is no rule that governs how channels must be created. There is no way to terminate that goroutine though. One use case this pattern fits well is reading a large resultset from a database. The channel allows streaming data as it is read from the database. In that case usually there are other means of terminating the goroutine though, like passing a context.

3. Again, there are no hard rules on how channels should be created/closed. A channel can be left open, and it will be garbage collected when it is no longer used. If the use case demands so, the channel can be left open indefinitely, and the scenario you worry about will never happen.