20,741
edits
Emesary: Difference between revisions
Jump to navigation
Jump to search
m
→Status: https://sourceforge.net/p/flightgear/mailman/search/?q=emesary
m (→Status: https://sourceforge.net/p/flightgear/mailman/search/?q=emesary) |
|||
| Line 11: | Line 11: | ||
|date = Apr 9th, 2017 | |date = Apr 9th, 2017 | ||
|added = Apr 9th, 2017 | |added = Apr 9th, 2017 | ||
|script_version = 0.40 | |||
}}</ref> | |||
Meanwhile, Richard has nearly finished his improvements to Emesary to make it easy and seamless to transmit properties over MP instead of the of the usual way. This is a two part set of changes, the first part (complete) is to transmit from the master model, the second part is still WIP and relates to the transmission back for dual control. On 13/06/2017 22:03, jsb wrote: > What is Emesary? At the highest level Emesary is a way of communicating information between objects that are otherwise unrelated and possibly separated by a physical (machine, network, process) boundary. http://chateau-logic.com/content/emesary-nasal-implementation-flightgear Two (or more) systems can be connected together by using a bridge; the bridge that I've implemented uses the generic string properties to transmit the messages transparently (to both the sender and recipient). http://chateau-logic.com/content/emesary-multiplayer-bridge-flightgear (documentation is possibly slightly out of date for the most recent developments that are in my fgdata) Richard Harrison has got the transmission of properties working ; using a new notification type.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35894463/ | |||
|title = <nowiki> [Flightgear-devel] Emesary / Multiplayer improvements </nowiki> | |||
|author = <nowiki> Richard Harrison </nowiki> | |||
|date = Jun 14th, 2017 | |||
|added = Jun 14th, 2017 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||