-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Umbra - AMQPUrlReceiver.java receive urls via amqp and add to frontier, related changes #38
Conversation
…rmat produced by https://github.com/internetarchive/umbra and add to frontier
…ting infinite consumers
…eaders"), if any, in http request
…status; add default amqpUri; replace queueName setting with exchange and routingKey, which seem to be what are needed; avoid sending urls that were received from AMQP, and robots.txt urls; set content-type of amqp message to application/json, which umbra seems to need
// "Note: all methods of this interface are invoked inside the Connection's | ||
// thread. This means they a) should be non-blocking and generally do little | ||
// work, b) must not call Channel or Connection methods, or a deadlock will | ||
// ensue. One way of ensuring this is to use/subclass QueueingConsumer." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is probably fine for the moment. Let's worry about optimizing when we identify a bottleneck clearly.
By and large this looks good to me. I still think we should also get this running under travis-ci or similar, that way we could to full round-trip tests with a rabbitmq server, but merging for now. |
Umbra - AMQPUrlReceiver.java receive urls via amqp and add to frontier, related changes
No description provided.