PLUMB MASTER

Brand Owner Address Description
PLUMBMASTER Plumbmaster, Inc. 2951 Highway 501 E. Conway SC 29526 PLUMB MASTER;Plumbing parts, namely, faucets for sink, tub and shower, faucet handles and faucet stems; faucet repair parts, namely, faucet components, aerators, lavatory pop-ups and linkages; toilet repair parts, namely, toilet flappers, tank levers, flush valves; flush valve repair parts, namely, ballcocks, ballcock repairs, namely, plungers, caps, float rods, refill tubes, seal rings, diaphragms, pistons, linkages; floats and tank balls, drain repair parts, namely, sink strainers, traps, bends, tubing, tailpieces and waste arms; drain stoppers, namely, bath stoppers; valves and fittings used in plumbing, namely, stops, supply tubes, brass fittings, namely, elbows, tees, couplings, unions, connectors, caps, nuts, iron fittings, namely elbows, tees, couplings, unions, connectors, caps, nuts, and plastic fittings, namely elbows, tees, couplings; tub and shower repair parts, namely, shower heads, shower escutcheons and nipples, shower arms, and personal shower hoses; heating (HVAC) repair parts, namely, radiator repair parts, namely, radiator valve handles, radiator air vents, electrical resistance elements for water heaters, steam valves and zone valves; electrical supplies, namely, light bulbs;
 

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.