SAUCES READY USE

Brand Owner Address Description
FA SAPEFA FERDINAND0 AURICCHIO S.R.L. Corso di Porta Vittoria 18 20122 MILAN Italy Sauces ready for use, tomato products, namely, tomato sauces for macaroni and spaghetti; frozen pizzas, frozen entrees consisting primarily of pasta or rice; coffee, rice, flours and preparations made of cereals, namely, breakfast cereals, oatmeal, muffins, cereal bars, cakes, biscuits, bread, cookies; pastries; pasta, bread, bread substitutives, namely, crackers and breadsticks, rusks, pastry, biscuits, cookies, waffles; bakery products, pastry and candies, ice-creams; vinegar, sauces, seasonings, spices; prepared meals consisting primarily of pasta or rice;Meat, fish, poultry and game, salami, sausages, ham, meat extracts, preserved, dried, cooked and frozen fruits and vegetables, jellies, jams, marmalades, compotes, eggs, milk and dairy products excluding ice cream, ice milk and frozen yogurt, tomato paste, tomato puree, peeled tomatoes, yogurts, ripe and fresh cheese, edible oils and fats, frozen entrees consisting primarily of meat, fish, poultry or vegetables, prepared meals consisting primarily of meat, fish, poultry or vegetables;FERDINANDO AURICCHIO;
 

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

    
Technical Examples
  1. Transactions are scheduled over a half duplex link between a first device, such as an IO unit, and a second device, such as a memory controller. Information flowing over the half duplex link is divided into a plurality of service periods, and an isochronous transaction, such as an isochronous memory read or write, is scheduled in a service period N if the isochronous transaction is ready to be serviced before service period N at the first or second device. An asynchronous transaction ready to be serviced at the first or second device, such as an asynchronous memory read or write, is scheduled if no isochronous transaction is ready to be serviced. The asynchronous transaction may be scheduled by (a) scheduling an asynchronous transaction ready to be serviced at the first device if no asynchronous transaction is ready to be serviced at the second device; (b) scheduling an asynchronous transaction ready to be serviced at the second device if no asynchronous transaction is ready to be serviced at the first device; and (c) scheduling an asynchronous transaction ready to be serviced at the first or second device, according to an arbitration algorithm, if asynchronous transactions are ready to be serviced at both the first device and the second device. The amount of buffer space available in the first or second device may also be used to schedule asynchronous transactions.