Skip to main content

Timeline for TCP connection and reconnection

Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Nov 3, 2015 at 21:22 history edited Jamal CC BY-SA 3.0
deleted 400 characters in body; edited tags; edited title
Aug 25, 2013 at 12:52 vote accept Zerowalker
Aug 25, 2013 at 11:20 answer added Glenn Rogers timeline score: 7
Aug 25, 2013 at 9:54 history edited Zerowalker CC BY-SA 3.0
Added some stuff
Aug 25, 2013 at 0:55 comment added Zerowalker Though, again, I can put the TCP Reconnecting in a Method, as that just takes place for no big reason.
Aug 25, 2013 at 0:12 comment added Zerowalker I had them in Methods before, but i don´t really like having codes all over the place when i can have then at the same place. Though if i reuse the code in alot of places, i do have them in methods. But here, there is really no reason for me to put it in a method or separate class. I can however put the Image Encoding in a separate thread.
Aug 24, 2013 at 23:18 comment added radarbob "that would probably slow things down" - A classic illustration of premature optimization mindset. The original question addresses a clear problem with the code and I assert debugging and maintenance in the current state will be much more of a problem than presumed performance degradation caused by refactoring. @svick's advice is sound. I suggest you start by "extracting to methods". As methods it is more flexible to re-work - getting to separation of concerns and manage the concern about "out of order."
Aug 24, 2013 at 20:11 comment added Zerowalker that would probably slow things down, as i am sending the image i take. If i seperate this, it would get out of order.
Aug 24, 2013 at 18:54 comment added svick First of all, you should apply separation of concerns. Encoding images and network communication shouldn't be in the same method, probably not even in the same class.
Aug 24, 2013 at 16:48 history asked Zerowalker CC BY-SA 3.0