JOURNEY MAN

Brand Owner (click to sort) Address Description
JOURNEYMAN Keyline Sales, Inc. Post Office Box 1861 Elkhart IN 46515 JOURNEY MAN;accessories for recreational vehicles, trucks, buses, boats, vans and automobiles; namely, storage trays and receptacles for affixation to vehicle;
JOURNEYMAN Seghesio, Cathy P.O. Box 1871 Healdsburg CA 95448 JOURNEY MAN;Wine;
JOURNEYMAN Seghesio, E. Peter P.O. Box 1871 Healdsburg CA 95448 JOURNEY MAN;Wine;
JOURNEYMAN Journeyman Distillery 109 Generations Drive Three Oaks MI 49128 JOURNEY MAN;rental of banquet and social function facilities for special occasions, namely, wedding receptions, birthday parties, celebrations and life cycle events;
JOURNEYMAN JOURNEYMAN MEAT COMPANY 3220 PASSALACQUA ROAD HEALDSBURG CA 95448 JOURNEY MAN;On-line wholesale and retail store services featuring meat; wholesale and retail store services featuring meat;
JOURNEYMAN Quality Bicycle Products, GBC. 6400 W. 105th Street Bloomington MN 55438 JOURNEY MAN;Bicycles;
JOURNEYMAN M & C INNOVATIONS 1829 Queens Road Charlotte NC 28207 JOURNEY MAN;Portable coolers, non-electric;
 

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

    
Technical Examples
  1. The fast dynamic measurement of connection bandwidth utilizes a single pair of packets to calculate bandwidth between two entities on a network (such as the Internet). This calculation is based upon the packet-pair technique. This bandwidth measurement is extremely quick. On its journey across a network, communication equipment and modems may compress a packet. This compression shrinks the size of the packet; thus, it can distort the bandwidth calculation using such a shrunken packet. To avoid this distortion, the fast dynamic measurement of connection bandwidth employs non-compressible packets. More specifically, it employs highly entropic packets. Therefore, a packet cannot be compressed during its journey. In addition, on its journey across a network, packets may be rerouted, delayed, misrouted, and the like. These momentary delays may result in a momentary bad bandwidth calculation. This problem is ameliorated by using a history list at the client that keeps track of recent measurements. The client returns the median of that list to the server. That median is the specified bandwidth.