Task #1804 (closed)
Opened 15 years ago
Closed 13 years ago
Web : Handle Protocol exceptions with "possible version mismatch error"
Reported by: | jamoore | Owned by: | wmoore |
---|---|---|---|
Priority: | minor | Milestone: | OMERO-Beta4.3.2 |
Component: | Web | Version: | 4.1 |
Keywords: | n.a. | Cc: | atarkowska |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | 2011-08-04 (2) |
Description
See #1803 for details.
Change History (4)
comment:1 Changed 13 years ago by atarkowska
- Milestone changed from Unscheduled to OMERO-Beta4.3.2
- Sprint set to 2011-07-21 (1)
comment:2 Changed 13 years ago by atarkowska
- Cc atarkowska added
- Owner changed from atarkowska to wmoore
comment:3 Changed 13 years ago by cxallan
- Sprint changed from 2011-07-21 (1) to 2011-08-04 (2)
Moved from sprint 2011-07-21 (1)
comment:4 Changed 13 years ago by wmoore
- Resolution set to invalid
- Status changed from new to closed
Since the web does not allow any connection if the versions don't match #5983, we shouldn't have to handle exceptions due to version mismatch.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Will is this still valid?