76
General Discussion / Re: Delegates Please Publish Prices for USD, BTC, and CNY
« on: September 01, 2014, 04:42:19 am »
upgraded and published the price feed.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
每天最后一个块时的数据,不是平均。y 轴数据怎么算?
this one does not use the real snapshot, just some keys I had. post for funds, a few people have them
Code: [Select]struct test
{
int a;
string b;
vector<string> c;
}
FC_REFLECT( test, (a)(b)(c) )
In binary converts to:
4 bytes for a
VARINT storing b.size()
b.size bytes string content of b
VARINT storing c.size()
for( c.size() )
{
VARINT storing c.size()
c.size bytes string content of c
}
it is difficult for me to understand the bitshares tookit serialization mechanism and technology, would be appreciated if anyone can provide some guidence /documentation
Sure... 100% of all serialization is managed by fc via the reflection system.
Looking at the structure definition is enough to infer the serialization.
Data is serialized in the order listed in the FC_REFLECT macro
Strings & Arrays are prefixed with a variable length int that uses the same encoding as google protocol buffers.
In binary terms the data is simply copied with the same byte order as the host.. ie: it will not work on big endian systems.
Check out FC_REFLECT and fc/io/raw.hpp which defines the "raw binary" serialization based upon reflection.
BTSX addresses are not used anywhere in the API... we use the public keys for the accounts, but there is no way to convert an address to a public key (address is hash of public key)
This actually makes a lot of sense.
And the init delegates were stable so far.
Perhaps they will prevent this for the future.
they will probably know once s.o. gets up .. anyway .. doesn't hurt the network too much as there are 101 delegates in total
BM already told them to fix the redundandy