can not broadcast to 255.255.255.255

[RavensFan · Accepted solution]

Try this.

(Note, there may be other ways of going about it.)

Message Edited by Ravens Fan on 08-26-2009 02:38 PM

[altenbach]

---

lavalava wrote:

Say I'm sending  0xAABBCCFF.  On the receiving, the UDP reader automatically converts 0xAABBCCFFto ASCII. 

---

OK, you are flattening your U32 number of xAABBCCFF to a string on the sending end. All you need to do is unflatten from string on the receiving end using a U32 diagram constant (value not important) as type and you get your U32 number back. And make sure to read only 4 bytes.

[altenbach]

---

lavalava wrote:

...but the problem is my parser is expecting 0xAABBCCFF. 

---

Let's take a step back, because it is irrelevant what the parse expects. All we need to know is what the parser should output on the other end given the existing binary string!

It would be very expensive to take the detour over formatted text, so let's not do that!

[altenbach]

Here are some alternatives to Raven's code FYI. Still, I strongly suggest not to take the detour over hex formattes strings!