MUD MASTER

Brand Owner (click to sort) Address Description
MUDMASTER DIAMOND SHAMROCK CHEMICALS COMPANY 717 N. HARWOOD ST. DALLAS TX 75201 MUD MASTER;OIL FIELD DRILLING FLUID ADDITIVES;
MUDMASTER Casio Keisanki Kabushiki Kaisha (Casio Computer Co., Ltd.) 6-2, Hon-machi 1-chome, Shibuya-ku Tokyo 151-8543 Japan MUD MASTER;Precious metals; jewellery ornaments, other than cuff links; cuff links; semi-wrought precious stones and their imitations; unwrought precious stones; wrist watches; watch bands and straps; dials for clock and watchmaking; cases for clock and watchmaking, namely, cases being parts of clocks and watches; clocks and watches; electric watches and clocks; electronic watches and clocks; parts and fittings for watches, clocks and wrist watches; wrist watches having a function of transmitting and receiving data to and from an electronic personal organizer, mobile phones and a personal computer; autonomous radio controlled watches; watches having a function of transmitting and receiving data; watches having a GPS function; chronographs for use as watches; stopwatches; timekeeping instruments, namely, timepieces; clock and watch hands; watch faces; watch movements; watch glasses; watch chains; watch boxes; watch pouches; table clocks; pocket watches; automobile clocks; wall clocks; alarm clocks; watch and clock springs; watch crystals; watch back covers; pendulums for clock and watchmaking;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. A persistent peer-to-peer network is implemented over a network with master-slave topology. Data being sent from master to slave or from slave to master are sent in one transmission, but data sent from one slave to another is received by the master and retransmitted to the slave. A session table is kept at each device includes an ordered list of devices, where the first device is the master device. When a master device drops out of the network the slave devices promote the next device in the ordered list of devices to master. A master device may also receive a request from a slave device to become master, and update its session table and send the updated session table to all devices. The slave device requesting master status is then treated as master by all devices in the network.