SUMMARY / RELATED TOPICS

Leucinodes ethiopica

Leucinodes ethiopica is a species of moth in the family Crambidae. It is found in Eritrea and Saudi Arabia; the species was described by Richard Mally, Anastasia Korycinska, David J. L. Agassiz, Jayne Hall, Jennifer Hodgetts and Matthias Nuss in 2015; the length of the forewings is 6 -- 8 mm for both females. The forewings are mixed white. There is an oblique dark ochreous fascia from above the dorsum reaching halfway across the wing, as well as a blackish crescent before the ochreous subterminal line and there are black dots along the termen; the hindwings are white with a small black discal spot, a faint irregular dark subterminal line and ochreous suffusion in the outer part of the wing in the middle and towards the apex. The species name refers to Ethiopia, where the holotype originates

Bolt (network protocol)

The Bolt Protocol is a connection oriented network protocol used for client-server communication in database applications. It operates over WebSocket. Bolt is statement-oriented, allowing a client to send messages containing a statement consisting of a single string and a set of typed parameters; the server responds to each statement with a result message and an optional stream of result records. Developed for use in the Neo4j graph database, Bolt was inspired by the binary network protocol of PostgreSQL and features a data interchange format derived from MessagePack; the protocol is published on the website https://boltprotocol.org. The Bolt protocol was first introduced to the public in November 2015, during an interview conducted by Duncan Brown and published on DZone; the first release of software implementing the protocol occurred in December 2015, as part of a milestone release of Neo4j Server. In April 2016, Neo4j Server 3.0 was released and contained the first server implementation of the protocol, accompanied by a suite of Bolt client drivers.

This release received attention from several mainstream media outlets. The protocol supports explicit version negotiation between the client and the server. There is only one published version of the protocol: version 1. Bolt clients and servers both send data over the connection as a sequence of messages; each message may include additional data. The client drives the interaction, each message sent by the client will cause one or more response messages to be sent by the server. Client messages: Server messages: Each message is encoded into a sequence of bytes; these bytes are transferred using a binary chunked encoding, where each chunk is preceded by an unsigned, big-endian 16-bit integer denoting the number of bytes that follow. A length of 0 is used to denote the end of the message. A client may send multiple messages without first waiting for a response; the server processes each message sequentially. However, as there may be logical dependencies between messages sent by the client, the server will not evaluate requests it receives after sending FAILURE in response to a preceding message.

Instead, it will send an IGNORED message in reply to every client message, until the client acknowledges the failure by sending an ACK_FAILURE message. This is similar to the failure recovery in the PostgreSQL wire protocol. Bolt supports encoding for a number of different data types. Bolt protocol specification