• 0

Bytes with TCP socket and bit manipulation


Question

I'm taking a computer communication summer class and this is our 2nd and last program project. The protocol for the assignment can be found here.

I've already done one project that involves a client and server connecting and playing a game of guess the number with strings being sent back and forth. For this project though we have to manipulate individual bits of bytes and send only bytes across the socket connection. How do you do this in Java? I haven't been able to find anything about forming bytes with particular bits and sending just bytes across the connection.

11 answers to this question

Recommended Posts

  • 0

I'm not sure what your project assignment is doing (I dont' have time to read it). But from my experience in Java, to read binary data you use InputStream or OutputStream to read and write binary data.

Here's an example:

Let's assume "sock" is your socket connection.

InputStream in = sock.getInputStream();
while (in.read() != -1)
{
     //do whatever you need to do with it
}

You can also look at sun's java api for more info (search for inputstream).

Hope this helps!

  • 0

I've read some of the things on the input and output streams and i'll be definitely be using them. My problem comes after I've received the bytes. I have to use certain control bytes as notifiers for things:

00000001- REQuest connection.

00000010 - CONnection Granted.

ssss0011 - FILe name packet (sequence number sss = 000).

ssss0100 - DATa Packet, where sss is the sequence number of the packet.

ssss0101 - Short Data Packet(SDP), where sss is the sequence number of the packet.

ssss0110 - ACKnowledgment packet, where sss is the sequence number of the packet expected next.

ssss 0111 - list request packet (sequence number sss = 000).

0000 1111 - TERmination (a simple two-way handshake).

After I've received the bytes I don't understand how to interpret the different bits of the bytes to know what I'm dealing with.

  • 0

You can AND them (note this is C-style code)

if(byte == 0x01) // REQuest connection
{
}
else if(byte == 0x02) // CONnection granted
{
}
else if(byte & 0x0F == 0x03) // FILe name packet
{
    sequence = (byte & 0xF0) >> 4;
}

  • 0

Thx for the info Andareed!

I've taken computer structures so I understand the idea of And'ing and Or'ing things but I don't quite understand the hex strings your using. Any extra tips on those? I tried google'ing some stuff but it didn't really help. Also, what exactly does the >> do.

Edit:

Since hex is 16 bits I'm guessing the first digit is the first 4 bits and when you check for 0x0F you're testing to see if the first 3 bits are all 1's to know it's a file packet and similarly for the others. The >> still confuses me though.

Edited by Little Moe
  • 0

I've run into another problem. When sending a packet with file information one of the bytes has to be a one-byte unsigned binary value. I've found a whole lot of stuff about doing unsigned bytes in Java by using ints and AND'ing stuff with 0x0FF but my I think my problem comes with actually sending the byte.

My teacher expects our clients and servers to run against his C clients and servers. He gave us an example exe of each and whenever I run my client against his it says "Number of char in file name should be between 1 and 124 - LEN field = 0" like it's not getting my byte at all. I'm thinking it's either the byte I'm using or something special in the OutputStream that might be messing up my byte? I know there is no difference between the bits of a signed or unsigned byte but something is going wrong. Does anyone have an example of sending a byte like he is asking or maybe if I'm thinking of this wrong.

  • 0

I ended up finishing the project. My biggest problem starting off was I was trying to send bytes individually by just writing the bytes one at a time. My teacher was expecting the bytes one right after another. I had to send a byte array for him to get everything in a packet that I wanted. Couldn't just test one byte at a time. Had to test things just by hardcoding byte array values to see what happened.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Report: Trump's T1 Mobile off to a rocky start with messy pre-orders by David Uzondu You might have heard by now that The Trump Organization, spearheaded by President Trump's sons, Donald Trump Jr. and Eric Trump, is launching yet another product to add to the collection. This time, it is a gold smartphone, the T1, and a companion wireless service. The whole operation is being pushed with the usual "America-first" bravado, but it seems they forgot to get the basics right. If you thought you could just hop online and secure your patriotic pocket computer, you are in for a nasty surprise, as the whole process appears to be fundamentally broken. A new report from 404Media details this chaos perfectly, as one of their writers tried to order one of the T1 phones. The goal was simple: pay the $100 preorder deposit and see what this thing is all about when it ships. What happened next was a masterclass in how not to conduct e-commerce. The website crashed, booted him to an error page, and then, for good measure, charged his credit card the wrong amount entirely, taking $64.70. And get this, he received a confirmation email saying his order would ship... despite never once being asked for his shipping address. It is, in his words, the "worst experience I've ever faced buying a consumer electronic product". To add insult to injury, when he tried to log into the new account, the site prompted him to create, and he was immediately met with yet another error page, locking him out. The shoddy experience is not just limited to the checkout. Neowin found a bunch of errors on the official product page. Sure, it boasts a big 6.8-inch Punch Hole AMOLED display with a 120Hz refresh rate and a 50MP main camera, which sounds nice on paper. But then you notice the company completely forgot to mention what processor powers the phone, which is probably a MediaTek. At one point, the page bizarrely listed a "5,000 mAh long life camera," though that has since been fixed. By the way, there's good reason to doubt that this phone will be made in America, despite the press releases insisting it will be. Sourcing all the necessary components without using foreign parts is unbelievably difficult and expensive, something even Apple does not do. The more likely scenario, according to Max Weinbach, is that this is simply a reskin of a much cheaper device, maybe the T-Mobile REVVL 7 Pro 5G, which retails at a fraction of the T1's $499 asking price. The T1 Mobile joins a sprawling collection of other products likely aimed at the same loyal customer. The catalog of gear for this audience already includes the gold "Never Surrender" sneakers, the "God Bless the USA" Bible, "Victory47" perfume, digital trading cards, $TRUMP memecoins, and more. It is still very early days, of course, and while one might forgive some teething issues for a new venture, this initial preorder phase has been exceptionally chaotic. Hopefully, things will become much clearer once there is a firm launch date and a physical product to test. Do you plan to buy the T1 and move to Trump Mobile?
    • Is this release set for the end of this year or for next year?
    • Windows 10 KB5063159 fixes bug that wouldn't let some Microsoft Surface devices boot by Sayan Sen Microsoft released Windows 10 Patch Tuesday updates for the month last week. The one for Windows 10 under KB5060533 / KB5060531 / KB5061010 / KB5060998 introduced a bug that would not let Surface Hub v1 devices start due to a Secure Boot validation issue. As such, Microsoft had paused the update similar to the compatibility blocks or safeguard holds it applies for major feature updates as well. This bug was uncovered after the update went live, as Microsoft later added it to the list of known issues for that update and it also put up a big notice in bold. It wrote: Earlier today, the company released an out-of-band (OOB) update to address the issue. It has been published under KB5063159 and is only being offered to Surface Hub v1 devices instead of the buggy KB5060533 Patch Tuesday one. In the description of the new OOB update, Microsoft writes: You can find the support article for KB5063159 here on Microsoft's website. It is downloaded and installed automatically but users can also manually download it from the Microsoft Update Catalog website.
    • I thought I saw that one, and yeah, it was awhile ago, too..
  • Recent Achievements

    • Week One Done
      korostelev earned a badge
      Week One Done
    • Week One Done
      rozermack875 earned a badge
      Week One Done
    • Week One Done
      oneworldtechnologies earned a badge
      Week One Done
    • Veteran
      matthiew went up a rank
      Veteran
    • Enthusiast
      Motoman26 went up a rank
      Enthusiast
  • Popular Contributors

    1. 1
      +primortal
      686
    2. 2
      ATLien_0
      268
    3. 3
      Michael Scrip
      184
    4. 4
      +FloatingFatMan
      177
    5. 5
      Steven P.
      140
  • Tell a friend

    Love Neowin? Tell a friend!