| Age | Commit message (Collapse) | Author |
|---|
|
This function can be used to seek an incoming file tranfer right
before accepting it.
It is meant to be used to resume incomplete file tranfers by clients.
|
|
Pointer in callback will be NULL if length is 0.
|
|
file_id is a 32byte identifier that can be used by users to identify
file tranfers across core/client restarts in order to resume broken
file tranfers.
In avatar tranfers it corresponds to the hash of the avatar.
Added tox_file_get_file_id() function to api to obtain the file_id
of an ongoing file transfer.
If not set, core will generate a random one.
|
|
|
|
first 32 bytes.
Enforce length of filename in core when transfer is an avatar type
transfer to make things more safe.
|
|
contents pointed by proxy_address.
|
|
|
|
|
|
|
|
This allows clients to agree on what numbers mean what without having
it be set in core.
|
|
in the requested chunk callback.
For zero size transfers if the data sent is not the same length, the
file is assumed to be done.
|
|
|
|
|
|
This is done so that the function now has the same parameters as the
request chunk callback.
|
|
The first commit's message is:
TOX_STATUS -> TOX_USER_STATUS, is more specific
This is the 2nd commit message:
I pretty strongly believe tox_iteration needs to be renamed to a verb
There are several other noun functions in the API, but none of them *do* things.
I think even tox_do is better than tox_iteration.
tox_do_interval is one possibility, but I'm open to suggestions.
This is the 3rd commit message:
private_key -> secret_key
This is more consistent with modern/NaCl/elliptic cryptography, and also "pk", meaning public key, is all over other toxcore code and documentation. This will eliminate ambiguity.
This is the 4th commit message:
Rename some functions for pseudo-namespace consistency
The enum change results in long enum types, but I think consistency trumps
having a few less characters.
This is the 5th commit message:
TOX_FILE_KIND -> TOX_FILE_TYPE
This is more of an English thing than a consistency thing, but
TOX_FILE_KIND sounds funnier/stranger to me than TOX_FILE_TYPE.
This is the 6th commit message:
More specific file control function names
This is the 7th commit message:
Rename custom packet functions for pseudo-namespace consistency
This also has the issue with long enums... but I still think consistent enum names are better
This is the 8th commit message:
Rename functions for pseudo-namespace consistency
This is the 9th commit message:
Consistency with https://github.com/sonOfRa/tox4j/blob/master/doc/core-design.md#naming-conventions and the rest of the api
This is the 10th commit message:
Fix errors in previous function rename commits
This is the 11th commit message:
Shorten one error enum name
|
|
Since the functions are not new api like I put them in tox_old.{c,h}
|
|
Everything should work except resuming.
|
|
|
|
new_api
|
|
|
|
|
|
|
|
(Done with two applications of "sed -i -r "s/(\\w+) const\\b/const \\1/g" toxcore/tox.*" )
Conflicts:
toxcore/tox.c
|
|
toxcore easier.
|
|
Some small self explainatory changes to the api.
|
|
m_copy_self_statusmessage no longer takes a buffer length argument.
|
|
|
|
|
|
|
|
TOX_CLIENT_ID_SIZE renamed to TOX_PUBLIC_KEY_SIZE.
Renamed client_id to public_ke in public api.
|
|
proxy_enabled with proxy_type.
|
|
|
|
|
|
|
|
|
|
https://github.com/wrouesnel/toxcore
|
|
Change the custom_packet_handler callback function interface to be
consistent with other callback interfaces.
The new interface takes the Messenger object calling as the first
parameter, and moves the user data object to be the last parameter.
This makes it comparable to the callbacks for file transfer and the
like, and should simplify building interfaces.
The new prototype is: int (*)(Messenger *m, int32_t friendnumber, const
uint8_t *data, uint32_t len, void *object)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
