| Anonymous | Login | Signup for a new account | 05-03-2024 02:07 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000383 | [Resin] | minor | always | 09-14-05 00:00 | 10-06-05 00:00 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | urgent | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.0.15 | Product Version | 3.0.14 | ||||
| Product Build | 3.0.14 | ||||||||
| Summary | 0000383: custom protocol enhancements | ||||||||
| Description |
RSN-429 (rep by Kirk Rasmussen) Is there a listener interface so that we can gracefully handle timeouts using the custom protocol architecture built-in to resin? |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0000442) ferg 09-14-05 00:00 |
For example, We can enforce a 4 minute timeout using this configuration but this simply closes the underlying connection. <port id='' host='*' port='8888' read-timeout='240s'> <protocol resin:type="example.Magic8BallProtocol"/> </port> Is there a way we can hook into the connection close event to handle proper cleanup on our end (e.g. multi-player game in progress)? Also we will need to broadcast messages (push messages to clients) without getting a request from the client first. I didn't see an easy way to do that with the API? |
|
(0000443) ferg 09-14-05 00:00 |
server/3200 |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 09-14-05 00:00 | ferg | New Issue | |
| 11-30-05 00:00 | administrator | Fixed in Version | => 3.0.15 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 27 unique queries executed. |  |
