MICO broker v2 Sample Clauses

MICO broker v2. ‌ During evaluation of the platform release and the first real usage of the system, it turned out that the communication channel between extractors to the broker had to be urgently extended: In broker v1, information about new content parts is the only data that the extractor could send to the broker. After getting a notification about new content, the broker then had to assume that the extractor finished pro- cessing successfully. However, if an extractor produced more than one new content part, all extractor errors apart from the first one would go unnoticed. Moreover, in this approach, extractors had to send a messages about new content parts, even when they did not provide any. Most importantly, the broker did not support the reporting and hence proper handling of errors during processing. Considering the urgency of such improvements, we decided to introduce an intermediate broker v2 with extended capabilities before implementation v3 in year 3. V2 improves the event API, which deals with broker-extractor communication: The broker uses it to send information to extractors when new content is added to the platform, to trigger the required extraction processes. Extractors use the API to store extracted metadata in the triple store, and to inform the broker about new extracted binary content after pushing it to the data store. A new message type was added to the event API to distinguish between following events during extraction processes: • new content part: As in v1, this is used by the broker to trigger next extractors for new parts. • extraction finished: Upon reception of this message, the broker can be sure that the extraction was successfully finished and the extractor is ready to process more content. • extraction aborted: This indicates that an extractor was not able to process content - this message can contain more detailed information about the reason why the process was canceled which can be used to detect and avoid problems, e.g. related to the content itself, problems with the environment such as insufficient disk space or memory, etc. • extraction progressed: This is an optional event, which is useful to indicate the progress in long- running processes. V2 was implemented for the Java event API, and is currently implemented for the C++ event API as well - it will be used by extractors until broker v3 is fully implemented.
Sample 1
AutoNDA by SimpleDocs

Related to MICO broker v2

  • No Broker Neither Seller nor any Affiliate of Seller has dealt with any broker, investment banker, agent or other Person, except for Buyer or an Affiliate of Buyer, who may be entitled to any commission or compensation in connection with any Transaction.

  • No Brokers The Company has taken no action which would give rise to any claim by any person for brokerage commissions, transaction fees or similar payments relating to this Agreement or the transactions contemplated hereby.

  • No Broker’s Fees Neither the Company nor any of its subsidiaries is a party to any contract, agreement or understanding with any person (other than this Agreement) that would give rise to a valid claim against the Company or any of its subsidiaries or any Underwriter for a brokerage commission, finder’s fee or like payment in connection with the offering and sale of the Shares.

  • INTRODUCING BROKERS In the situation where you have been introduced to us by an introducing broker, you consent to us exchanging information with that introducing broker for the purposes of this clause 28. You may withdraw your consent by advising us accordingly in writing.

  • Disputes between an Investor and a Contracting Party (1) Any dispute concerning an investment between an investor of one Contracting Party and the other Contracting Party shall, if possible, be settled amicably.

  • Financial Advisors No Person has acted, directly or indirectly, as a broker, finder or financial advisor for Purchaser in connection with the transactions contemplated by this Agreement and no Person is entitled to any fee or commission or like payment in respect thereof.

  • Settlement of Disputes between an Investor and a Contracting Party (1) Any dispute between an investor of one Contracting Party and the other Contracting Party in relation to an investment of the former under this Agreement shall, as far as possible, be settled amicably through negotiations between the parties to the dispute.

  • Investors of one Contracting Party affected by expropriation shall have a right to prompt review, by a judicial or other independent authority of the other Contracting Party, of their case and of the valuation of their investments in accordance with the principles set out in this Article.

  • WHOLE AND ONLY AGREEMENT 34.1 The Parties hereby confirm that this Agreement constitutes the whole and only agreement between them with regard to the subject matter of this Agreement.

  • Broker Each Note Holder represents to each other that no broker was responsible for bringing about this transaction.

Time is Money Join Law Insider Premium to draft better contracts faster.