jNabServer documentation “As Nabaztag uses HTTP-protocol to communicate with jNabServer it means that network architecture is relative simple. Cycle of one HTTP request starts from Nabaztag. Nabaztag asks for one of the possible files from jNabServer. These request are more detailed explained in requests part of documentation. In jNabServer MicroServer socket server receives this call and passes it to new Worker class. Worker class parses request. If request is bootcode or locate request it creates response and sends it to Nabaztag. After sending data connection is closed and Worker terminated. If request was any other type than bootcode or locate it is passed to Nabaztag class. If Nabaztag has any pending forced packets it sends one of them and Worker is terminated. If Nabaztag class doesn’t have any pending forced packets it parses request and passes call to correct method in plugin. After correct method has been called Nabaztag tells plugin to send data.”