[Mono-bugs] [Bug 36226][Nor] New - UdpClient can't determine IPEndPoint on receive

[bugzilla-daemon@rocky.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by taras.judge@shaw.ca.

http://bugzilla.ximian.com/show_bug.cgi?id=36226

--- shadow/36226	Wed Jan  1 23:44:38 2003
+++ shadow/36226.tmp.8998	Wed Jan  1 23:44:38 2003
@@ -0,0 +1,47 @@
+Bug#: 36226
+Product: Mono/Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: taras.judge@shaw.ca               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: UdpClient can't determine IPEndPoint on receive
+
+Please fill in this template when reporting a bug, unless you know what you 
+are doing. 
+Description of Problem: 
+ 
+ 
+Steps to reproduce the problem: 
+The following is valid in Rotor using csc...Compiles and runs 
+UdpClient udp = new UdpClient(8080); 
+IPEndPoint from = null; 
+byte []buf = udp.Receive(ref from); 
+Actual Results: 
+Mono runtime refuses to accept a null value of "from". 
+ 
+ 
+Expected Results: 
+In rotor when from is null if is filled in with info from origin of the packet. 
+ 
+ 
+How often does this happen?  
+ 
+ 
+Additional Information: 
+For example download http://glek.net/~taras/rider.cs 
+do clix rider.ex & 
+clix rider.exe -a  
+to test it and see it working under ms stuff. 
+ 
+Also, udp packets in mono are limited to an arbitrary number :1024(which is 
+just ridiculous)