|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2291 | minor | always | 01-07-08 07:34 | 01-07-08 16:13 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.5 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.5 | ||
|
|
|||||
| Summary: | 0002291: flash policy file protocol | ||||
| Description: |
(rep by Vic Cekvenich) known for push, which I have now re-implemented using Hessian comet w/ Resin w/ help from Emil. It seems that it should be able to work on port 80, thus not having any corporate firewall/proxy issues. But that requires that "server listening on that port must understand socket policy file requests... and must respond differently for policy file requests and main connection requests" (from this page http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security_04.html [^] ). Currently resin configuration file can talk on another port.... however, working on port 80 for a "socket server" would be huge, at least for our needs. So.. that would be a feature request, get resin to recognize this flash "socket policy file request" and/or ... get entire Hessian conversation to be on port 80 even for Comet, at least for the Pro customers. (Hessian w/o Comet already works on any port). |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||