Actually Amazon's service is rock solid. They have some of the
biggest hosting centers around spread all over the world. What's
queued is encrypted and confidential. They're just providing a
service just like any hosting center would provide a SAN or fail-over
hardware or anything else. The only difference here is they are
providing the service remotely via SOAP. They also have Amazon S3
file hosting SOAP service too which is rockin'.
On Aug 30, 2006, at 1:00 PM, Phil Tomson wrote:
On 8/30/06, Peat Bakke <[EMAIL PROTECTED]> wrote:
So, here's a weird idea -- how would they feel about using Amazon's
Simple Queueing service as the middleware? There's wrappers in Java
and Ruby. It doesn't solve the local caching issue, but that's
pretty
easy to wrangle in Ruby or Java.
Not likely good as there will be confidential information transferred.
There will likely be encryption, though. But we're talking about
another large corporation here and they likely wouldn't want to rely
on something going through Amazon's servers (unless I'm
misunderstanding something about Amazon's Simple Queueing service).
Phil
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
