Category: z_techMiscInet

A blockchain is a peer-to-peer network that timestamps records by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work.

In contrast, a distributed ledger is a peer-to-peer network that uses a defined consensus mechanism to prevent modification of an ordered series of time-stamped records. All blockchains are distributed ledgers, but not all distributed ledgers are blockchains.

Keywords:

Peer-to-peer — no central single-point-of-failure
Immutable — records of past transactions
Ever-growing — the chain keeps growing and never shrinks
Double-spend — is a common error to be prevented by blockchain

Now I feel an http response may be a zip containing multiple files. The response “body” will be an compressed bytes array. (To avoid confusion, I will call this a “zip” rather than a “file”.) When you parse these bytes, you may see multiple zip entries.

If you assume the entire zip is a single file and try to decompress/deflate it, it might fail. The output may be empty.

The http response also contains useful response headers. One of the headers would be content-type. The gzip and zip types seem to require different parsers.

Q: what's a “selector”, in one sentence of plain english?A: bit of a CSS definition that says what the styles are applied to

Q: 3 basic types of selectors?A:* HTML Elements, such as

tags, tags etc.* Elements with a specific class, for example an element with theclass “mystyle” (

)* Elements with a specific ID, for example an element with the ID“myparagraph” (

)

Q: pseudo selectors's signature, purpose, eg?A: Examples of this are link states (unused, visited, active) andfirst lines and letters. The selector has a colon after it with thestate before the definition. An example of this is the CSS definitionfor changing the colours of link colours:

In LDAP, the situation is slightly more complicated. Names are built from components that are separated by commas (“,”). Like DNS names, they read from right to left. However, components in an LDAP name must be specified as name/value pairs. The name “cn=Todd Sundsted, o=ComFrame, c=US” names the person “cn=Todd Sundsted” in the organization “o=ComFrame, c=US.” Likewise, the name “o=ComFrame, c=US” names the organization “o=ComFrame” in the country “c=US.”