Bump to version 0.7.5-NB

WebsocketRailsClient++ (v0.7.5-NB)

This version with the abbreviation NB is a non blocking message handler version. This NB version handles every incoming message in an own thread. Why? If the incoming message gets dispatched and executes a callback, the callback can take an unknown amount of time. This blocks the complete incoming message handler. So, packages like ping-pong may be lost and the connection closes.

Changelog

• Solves bug in channel unsubscribe.
• Code rework.

Bump to version 0.7.4-NB

WebsocketRailsClient++ (v0.7.4-NB)

This version with the abbreviation NB is a non blocking message handler version. This NB version handles every incoming message in an own thread. Why? If the incoming message gets dispatched and executes a callback, the callback can take an unknown amount of time. This blocks the complete incoming message handler. So, packages like ping-pong may be lost and the connection closes.

Changelog

• Solves big bug in channel management.
• Code rework.

Bump to version 0.7.4

WebsocketRailsClient++ (v0.7.4)

Changelog

• Solves big bug in channel management.
• Code rework.

Bump to version 0.7.3-NB

WebsocketRailsClient++ (v0.7.3-NB)

This version with the abbreviation NB is a non blocking message handler version. This NB version handles every incoming message in an own thread. Why? If the incoming message gets dispatched and executes a callback, the callback can take an unknown amount of time. This blocks the complete incoming message handler. So, packages like ping-pong may be lost and the connection closes.

Changelog

• Solves many bugs.
• Solves segmentation fault if using channels reconnect.
• Solves deadlock in channel queue.
• Code rework.

Bump to version 0.7.3

WebsocketRailsClient++ (v0.7.3)

Changelog

• Solves many bugs.
• Solves segmentation fault if using channels reconnect.
• Code rework.

Bump to version 0.7.2-NB

WebsocketRailsClient++ (v0.7.2-NB)

This version with the abbreviation NB is a non blocking message handler version. This NB version handles every incoming message in an own thread. Why? If the incoming message gets dispatched and executes a callback, the callback can take an unknown amount of time. This blocks the complete incoming message handler. So, packages like ping-pong may be lost and the connection closes.

Changelog

• Solves blocking message handler.
• Solves many bugs.
• Solves segmentation fault if using channel subscribe and callbacks.
• Adds unsubscribe function with callbacks.
• Code rework.

Bump to version 0.7.2

WebsocketRailsClient++ (v0.7.2)

Changelog

• Solves many bugs.
• Solves segmentation fault if using channel subscribe and callbacks.
• Adds unsubscribe function with callbacks.
• Code rework.

Bump to version 0.7.1

v0.7.1

Bug in channel isPrivate().

Bump to version 0.7.0

v0.7.0

Change version in title.

Bump to version 0.7.0-beta

v0.7.0-beta

Resolves connection close problem if it is not connected.