You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code is super readable, to the point, and encapsulated perfectly..
The whole implementation is just an object with getters and setters...
sender uses setters, receiver uses getters & the constructor --
so i literally just read the datagram from the socket and throw it to the constructor...
AWESOME..
But my question is, what changes would I need to make to support rfc-2250.
Which getters and setters would need to change to support 2250?
Thanks!!
The text was updated successfully, but these errors were encountered:
g00dnatur3
changed the title
Assolutely LOVE the code, great job! Help with RFC-2250
Absolutely LOVE the code, great job! Help with RFC-2250
Feb 17, 2017
Honestly, when I originally wrote this 6.5 years ago, it was more of a proof-of-concept to be able to send/receive RTP audio packets in node rather than be a real full-fledged module. With that in mind, I don't have any plans to make any changes to this code. There are probably more complete modules available on npm these days.
This code is super readable, to the point, and encapsulated perfectly..
The whole implementation is just an object with getters and setters...
sender uses setters, receiver uses getters & the constructor --
so i literally just read the datagram from the socket and throw it to the constructor...
AWESOME..
But my question is, what changes would I need to make to support rfc-2250.
Which getters and setters would need to change to support 2250?
Thanks!!
The text was updated successfully, but these errors were encountered: