Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A few questions #1

Closed
Partixel opened this issue Apr 24, 2015 · 2 comments
Closed

A few questions #1

Partixel opened this issue Apr 24, 2015 · 2 comments

Comments

@Partixel
Copy link

  1. Are corrupted packets re-sent ?
  2. Which would be faster; Table serialised with vON then sent as a string or Table sent using :Table()
  3. I assume I can distribute this within a sold gmod addon as with vON, just want to make sure ?
@vercas
Copy link
Owner

vercas commented Apr 24, 2015

vNet doesn't do anything as far as channel reliability is concerned. The
Source networking protocol that Garry uses for net library does.
I believe that a net message that didn't arrive or arrived too late (after
the 'next' message) will really mess things up.
This is unlikely to happen, though. It never happened to me while testing.

As far as tables go, the :Table function is much faster and more
space-efficient than vON. It also supports more data types.
If your table is already encoded with vON (e.g. loaded from a file), I
recommending sending that, as a string. This will avoid re-encoding (and
possibly a decoding before that) and a file buffer.

And yeah, you are free to use vNet commercially as long as you give me
proper credits in the about/credits area of your addon.
On 24 Apr 2015 8:22 am, "Partixel" notifications@github.com wrote:

Are corrupted packets re-sent ?
2.

Which would be faster:

Table serialised with vON then sent as a string

or

Table sent using :Table()

  1. I assume I can distribute this within a sold gmod addon as with
    vON, just want to make sure ?


Reply to this email directly or view it on GitHub
#1.

@Partixel
Copy link
Author

Okay, I have done. Thanks for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants