Good catch on the re-slicing! Thanks!

I'll take another look at that section of code. What I was hoping to do was
avoid any type of explicit locking if I could, to use channels as a locking
mechanism instead. I may need to take another peek at Amir's example and
his talk again to see what I missed.
On Wednesday, 29 May 2013 13:53:36 UTC-7, Rob Thornton wrote:

After watching Amir's excellent Google IO talk I decided I wanted to
create a more novice, or at worst intermediate, approach. I've been working
on trying to create a simple, somewhat newbie friendly example of a
client/server. However, since concurrency is not a strong suit, and I'm
still a newbie myself, I'm hoping to get some feedback and suggested
improvements on them. They are working as intended but I worry that some
improvements will need to be made to ensure they are fairly robust and have
no resource leaks.

The goal was to develop a system which was as bare-bones as possible while
still demonstrating the power of Go and it's concurrency model. I tried
very hard to not have any distractions of message marshaling or a UI of any
kind. Just a proof of concept of a very, very simple client-server

The code can be found here: https://github.com/rthornton128/schat

I thank anyone in advance who does me the honor of taking a look and maybe
providing some feedback for me. I'd really appreciate it.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 5 | next ›
Discussion Overview
groupgolang-nuts @
postedMay 29, '13 at 8:53p
activeMay 30, '13 at 6:00p

2 users in discussion

Rob Thornton: 3 posts Martin Schnabel: 2 posts



site design / logo © 2022 Grokbase