The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
| Tag Class | Total number of occurrences | Tag strings used by tag class |
|---|---|---|
| @todo | 0 | @todo |
| TODO | 8 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 8
| org.bitrepository.common.utils.FileUtils | Line |
|---|---|
| verify, that it has successfully been removed. | 119 |
| org.bitrepository.common.utils.StreamUtils | Line |
| move to a utility class. | 43 |
| org.bitrepository.protocol.FileExchange | Line |
| Interface is extremely HTTP-centric. Should be generified. HTTP-centricity shines through to usage. | 40 |
| org.bitrepository.protocol.activemq.ActiveMQMessageBus | Line |
| Switch to use a session pool/producer poll to allow multithreaded message sending, see https://sbforge.org/jira/browse/BITMAG-357. | 77 |
| org.bitrepository.protocol.fileexchange.TestFileStore | Line |
| Auto-generated method stub | 155 |
| org.bitrepository.protocol.http.HttpFileExchange | Line |
| perhaps make it synchronized around the URL, to prevent data from trying to uploaded several times to the same location simultaneously. | 186 |
| org.bitrepository.protocol.http.HttpsFileExchange | Line |
| needs some SSL stuff?? | 62 |
| org.bitrepository.protocol.performancetest.MessageBusNumberOfListenersStressTest | Line |
| Important note for testers: The number of listeners should be regulated through the 'NUMBER_OF_LISTENERS' constant. When using many listeners, the DEFAULT_WAIT_TIME should be increased, e.g. 5000 for 25 listeners and 15000 for 100 listeners. Otherwise it is not ensured, that all the messagelisteners will receive all the messages before the validation. | 50 |
