• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
thekiwimaddog

Sending A Hash List

6 posts in this topic

Hi everyone!

I need to send a Hash List from a client to a server and was wondering on the best way to do this. I have a connection to the server and can send data fine but I was wondering how I should handle the procedure. I'm using TCP and was wondering if I could just get the client to just fire the data one Hash at a time and allow it to queue up on the server end. I'll be sending over a thousand of them and was wondering if I was just to send a load of seperate messages if it would be considered hammering the server?

Should I get the server to send a confirm message after it's received eash hash and then force the client to wait for the confirm before sending the next data. I want the data to be sent as quick as possible so I'd rather not have to wait for a confirm before each message.

Thanks in advance!
David
0

Share this post


Link to post
Share on other sites
When you already use TCP, you have a reliable stream. If you need some kind of messaging, just send a start message, then stream the whole map (key/value) and finally a end-message. There's no need of a confimation message, if the communication breaks, you will get an according error message from the TCP implementation.
1

Share this post


Link to post
Share on other sites
Thanks for your quick reply!

OK, maybe I'm not understanding how this works. I'm sending data using the send() function. Does it matter how often I make calls to this function? Once I've made a connection to the server can I send data as fast as I like without worrying about hammering the server or overloading any buffers? Or should I put the hash list into a single buffer and send just once? or would multiple calls to the send() function just join them up anyway?

Thanks
David
0

Share this post


Link to post
Share on other sites
send() will send at least one byte, but may not send all the bytes in the buffer. As long as you handle this case (re-sending the parts that weren't sent the first time,) you're good.

There is both buffering and flow control built-into TCP. The server will not actually receive data faster than it can handle it. Once the client tries to send more than the server can handle, the client's outgoing buffer will fill up, and send() will either start sending less than you asked it to, or will block and pause the client until space frees up. In either case, data won't flow across the wire faster than the server can deal with it.
1

Share this post


Link to post
Share on other sites
OK, so lets say I max out the buffer and the send() function only queues half the data that I sent to it. What's the best way to handle this? Do I have to keep retrying the send with the remaining data?
Is there a way to make it only queue the data if the full buffer is accepted because I'd rather not have to hang on a partial send and resend the whole message when the buffer is free.

Thanks
David
0

Share this post


Link to post
Share on other sites
[quote]Do I have to keep retrying the send with the remaining data?
[/quote]

Yes.

send() is guaranteed to make at least some progress each time you call it, so a tight loop that just calls send() and updates the send pointer will eventually terminate (assuming you break out of the loop if send() returns error.)

If you are on Linux, you can use write() instead of send(); write() will block until all the data is sent, or the socket has an error.
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0