Opened 16 years ago
Closed 16 years ago
#867 closed Bug (Fixed)
UDPRecv no longer gives the sender IP
Reported by: | martin | Owned by: | Jpm |
---|---|---|---|
Milestone: | 3.3.1.0 | Component: | AutoIt |
Version: | 3.3.0.0 | Severity: | None |
Keywords: | UDPRecv | Cc: |
Description
This request is very similar to ticket #131 which was rejected because it was said that the IP could be made a global variable, but that reason was incorrect.
In production version 3.2.0.0 UDPRecv set the sender's IP in the third element ([2]) of the array returned by UDPBind. This allowed you to determine the sender and reply appropriately. This feature has been removed so that it seems that the only way to find the sender is to require that the sender adds a header to the data, with the header containing his IP. Since the IP of the sender is already included in the data packet it seems reasonable to me that the UDPRecv function should reveal it.
In versions of AutoIt 3.3.0.0 and probably earlier, the third element is used for the receiver's IP which is not useful as that is known when UDPBind is called, it won't change and it could indeed be covered with a Global variable.
My request, obviously, is to have this feature returned.
It seems that the feature was never documented so it isn't a bug.
I appreciate that the feature might have been removed because it was considered better to only have one ip sending to one port and if so then I can understand the reason for rejecting this request.
Thank you for your time.
martin
Attachments (0)
Change History (6)
comment:1 Changed 16 years ago by TicketCleanup
- Version Other deleted
comment:2 Changed 16 years ago by Jpm
Nothing change in this area for a long time UDPRecv never return IP. It is an input info contain in the socketarray parameter.
So please post a script that will document what you expect as a new feature.
comment:3 Changed 16 years ago by Jpm
- Resolution set to No Bug
- Status changed from new to closed
comment:4 Changed 16 years ago by Jpm
- Resolution No Bug deleted
- Status changed from closed to reopened
comment:5 Changed 16 years ago by Valik
- Type changed from Feature Request to Bug
- Version set to 3.3.0.0
Changed to a bug report.
comment:6 Changed 16 years ago by Jpm
- Milestone set to 3.3.1.0
- Owner set to Jpm
- Resolution set to Fixed
- Status changed from reopened to closed
Fixed in version: 3.3.1.0
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Automatic ticket cleanup.