You can have timing without having a real time clock. Real time clocks strongly imply persistence between power cycles.
On Fri, Aug 9, 2013 at 4:35 AM, Ruud van Gaal <[email protected]> wrote: > Running ENet without some kind of timing? I'd say that would be pretty > hopeless of trying to achieve, as ENet is targeted to handling resends of > packets. For which you need, well, something that is time to make any sense. > > > On Thu, Aug 8, 2013 at 11:00 PM, Doug Warren <[email protected]>wrote: > >> And actually from Patricks point of view that's even worse. What if the >> embeded device has no RTC then every random seed on startup would be the >> same. Perhaps enet_random_entropy() in each platform would be more clear. >> >> >> On Thu, Aug 8, 2013 at 1:18 PM, Lee Salzman <[email protected]> wrote: >> >>> Not quite, enet_time_get() is for returning a running time counter, and >>> is not really intended for providing a time-differentiated random seed. If >>> you start up enet in quick succession making connections, then the random >>> seeds can more easily accidentally overlap. The idea here is to get actual >>> time in seconds so that on successive startups of enet the chance of >>> collisions is much smaller. And it's intended that time() is pretty >>> standard, and originally that's all that was used... Except that Win32 in >>> its usual rebelliousness, doesn't quite like this without linking against >>> more extra libraries, so I opted for timeGetTime() there. Chill out. It's >>> not the end of the world. >>> >>> >>> On 08/08/2013 10:56 PM, Patrick Klos wrote: >>> >>>> On 8/8/2013 2:00 PM, Doug Warren wrote: >>>> >>>>> You'd have to define your terms a bit better. It's straight C, if you >>>>> have berkley sockets and anything even vaguely resembling POSIX there >>>>> should be no need for extra support. I use the same build scripts for >>>>> iOS/Android/OSX/Linux. >>>>> >>>> >>>> The platform in question uses lwIP <http://savannah.nongnu.org/** >>>> projects/lwip/ <http://savannah.nongnu.org/projects/lwip/>> (a >>>> lightweight IP stack). Not real close to POSIX, but the basic functions >>>> are there. It's not quite _extra_ support, but it's _different_ support. >>>> I have it essentially working. >>>> >>>> >>>> >>>> https://github.com/lsalzman/**enet/blob/master/host.c<https://github.com/lsalzman/enet/blob/master/host.c>shows >>>> a single check for a platform specific check regarding how to get a >>>>> uint32 timestamp. >>>>> >>>> >>>> Which is completely unnecessary when the platform abstraction layer >>>> (win32.c and unix.c) provides the enet_time_get() function!?! It doesn't >>>> make sense why that function wouldn't be used? >>>> >>>> Patrick >>>> >>>> >>>> >>>> ______________________________**_________________ >>>> ENet-discuss mailing list >>>> [email protected] >>>> http://lists.cubik.org/**mailman/listinfo/enet-discuss<http://lists.cubik.org/mailman/listinfo/enet-discuss> >>>> >>> >>> ______________________________**_________________ >>> ENet-discuss mailing list >>> [email protected] >>> http://lists.cubik.org/**mailman/listinfo/enet-discuss<http://lists.cubik.org/mailman/listinfo/enet-discuss> >>> >> >> >> _______________________________________________ >> ENet-discuss mailing list >> [email protected] >> http://lists.cubik.org/mailman/listinfo/enet-discuss >> >> > > _______________________________________________ > ENet-discuss mailing list > [email protected] > http://lists.cubik.org/mailman/listinfo/enet-discuss > >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
