• 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.

Archived

This topic is now archived and is closed to further replies.

genovov

Another UDP question

7 posts in this topic

Well, I''ve looked in the windows socket documentation, the unix-socket faq and a bunch of tutorials, and can''t find the answer. What exactly does it mean when select() returns indicating a non-blocking UDP socket is available for writing? Does it mean that a single packet (smaller than the max packet size) can be writen to the socket safely? Or can any combination of packets be writen to the socket, as long as their total size does not exceed the max packet size? Or does it have another meaning? Should I check the return value to sendto(), even if select has indicated the socket is ready for a write? Thanks -genovov
0

Share this post


Link to post
Share on other sites
No one knows the answer? Does anyone have any ideas where I might be able to find the answer? Any good, advanced socket resources on the web?

Thanks again everyone,

- genovov
0

Share this post


Link to post
Share on other sites
I believe it means that the outbound buffer on that socket is empty.

That is to say once you''ve called a sento() on the socket, the function returns immediately as it is non-blocking. However, the data isn''t flushed immediately, so the select statement will signal when it has been flushed.
0

Share this post


Link to post
Share on other sites
Does that mean that it''s only possible to send one UDP packet between calls to select()?

Sorry if I''m being thick. I just want to figure out if I''ll need some kind of queue for outgoing packets...

Can anyone point me to some source that uses non-blocking udp sockets?

- genovov
0

Share this post


Link to post
Share on other sites
No, it doesn''t mean you can''t call more than one sendto() between select() calls. But it is possible to overflow the buffers if you don''t synchronize with the select calls. I believe if you do a buffer overflow on a non-blocking sendto() it will give some sort of error condition, either not the full length will be sent or some other explicit error condition.
0

Share this post


Link to post
Share on other sites
I didn''t see it specified as part of ther Berkley spec, or the Winsock 2 API docs. It''s probably one of those popular ''features'' of Sockets programming that is Implementation Specific.

To me, ''proper'' working order would mean that you should be able to send up to SO_MAX_MSG_SIZE bytes after a return of FD_WRITE from select(). If I get ambitious today, I''ll write some code to test it and post it here.
0

Share this post


Link to post
Share on other sites
I''m planning on porting my project when it''s finished, and was hoping this behaviour was defined in the spec. If you have a working version of Linux available to you, I would be very grateful if you could test how UDP behaves. I''ll do the same for winsock 1.1 over the weekend, and post the results here.

Does SO_MAX_MSG_SIZE include the size of the UDP header, or does it just refer to the data? If so, it may be that you can write SO_MAX_MSG_SIZE - ([number of calls to sendto()] * [UDP header size]) bytes after a call to select().

- genovov
0

Share this post


Link to post
Share on other sites
Ok, the spec says that select() will return with FD_WRITE set when send() or sendto() is guaranteed to succeed, so at least SO_MAX_MSG_SIZE bytes must be available in the buffer.

SO_MAX_MSG_SIZE refers to the maximum size of an individual datagram in the underlying transport layer. I believe that it doesn''t include headers. Therefore potentially multiple sendto()''s can be called with size up to SO_MAX_MSG_SIZE. SO_MAX_MSG_SIZE doesn''t refer to the buffer size for the socket.
0

Share this post


Link to post
Share on other sites