Uploaded image for project: 'REEF'
  1. REEF
  2. REEF-1835

Use stricter type constraints in Avro ProtocolSerializer

          Details

          • Type: Improvement
          • Status: Resolved
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 0.16
          • Component/s: Wake.NET

            Description

            Current version of ProtocolSerializer.Read() method accepts any type for the observer parameter, while internally it is always assumed to be of type IObserver<MessageInstance<?>>. We need tighter type constraints here - at least in the user-facing API.

              Attachments

                Activity

                  People

                  • Assignee:
                    motus Sergiy Matusevych
                    Reporter:
                    motus Sergiy Matusevych
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Time Tracking

                      Estimated:
                      Original Estimate - 8h
                      8h
                      Remaining:
                      Remaining Estimate - 8h
                      8h
                      Logged:
                      Time Spent - Not Specified
                      Not Specified