<p>At some point, I'd like to take out the kind of hacky self::$debug stuff and integrate with Zend_Log. I just found it useful to see how the stream was actually being called to help with building the methods. This class attempts to support GET Ranges as well because user-based streams limit to 8192 bytes being returned, even though it seemed Amazon was returning the full object size and ignoring my Range headers. Not too sure what was going on, but the class works regardless.</p>

<p>+1 (great work!)</p>

<ac:macro ac:name="note"><ac:parameter ac:name="title">Zend Comments</ac:parameter><ac:rich-text-body>
<p>This proposal has been approved for laboratory development with the following suggestion:</p>
<ul>
<li>Watch use of static members, underscores in variable names and class members, hardcoded behavior for mime-type detection based on filename, opportunity for generalized filesystem storage component (e.g., with Nirvanix and S3 as available backends), and integration with Zend_Log.</li>
</ul>
</ac:rich-text-body></ac:macro>

<p>Hi,</p>

<p>first of all I'd like to say I appreciated your work on this component and I'll use it as soon as it made it to the core. Anyhow I would prefer an API close to the S3-SOAP-Interface because it would be much easier to port existing code to use Zend_Service_Amazon_S3 and I don't like to create aliases for already existing method names (like mkdir vs. putBucket). I can only hope you reconsider the interface of your class <ac:emoticon ac:name="smile" /></p>

<p>hey, EXCELLENT WORK. Why is this not on the zend framework ? Everybody needs this !</p>

<p>Hey, It's just bad to let this in the incubator. I've posted a few mails in the mailing list in order to get this project going. There are 2 proposals for an s3 component and dozens of messages arround from guys asking for this. <br />
You've done an excellent work and it's been nearly a year since it's there lying in the incubator. It's not fair !</p>

<p>Amazon S3 support is a great idea! I think this service is much needed, and people have been asking for it. But I have concerns for the proposed API.</p>

<p>I am a massive proponent for not creating OO interface for OO's sake, but I am also a massive proponent of consistent API's. To me, the primary interface for this service component should consistent with the rest of the framework. This means that there should be accessors & mutators (setters & getters), as well as verb'd action names that "do work".</p>

<p>I am all about using php's strengths, and I think a stream wrapper should definitely be part of this component, but not as the primary api.</p>

<p>I feel like the primary class Zend_Service_Amazon_S3 should look and feel like the other service classes with respect to the api, and <strong>stay true to the concepts exposed by the API</strong>:</p>

<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
class Zend_Service_Amazon_S3

]]></ac:plain-text-body></ac:macro>

<p>Beyond that, I think its perfectly acceptable to create a stream wrapper class to expose this service as a custom stream:</p>

<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
$s3 = new Zend_Service_Amazon_S3();
// stream name should be dynamic so that multiple accounts are possible
$s3->registerAsStream($streamName);
]]></ac:plain-text-body></ac:macro>

<p>As you can see, the stream wrapper class (Zend_Service_Amazon_S3_StreamWrapper) would be used to be the "proxy" Between the actual s3 object and php's stream internals.</p>

<p>I guess thats all for now <ac:emoticon ac:name="smile" /></p>

<p>-ralph</p>

<p>Hi Guys,</p>

<p>Congratulations to everyone for their work on this component so far. I'd have to say though that I agree with Ralph. I feel the stream wrapper is definitely important - in fact required for this component, but it should not be the primary API. Also as Ralph mentioned the $s3->registerAsStream method would allow for multiple accounts, which in itself may be fairly important for some users as well.</p>

<p>Looking at the repository it seems we still need to finish the tests?</p>

<p>Cheers,</p>

<p>Rob</p>

<p>I'd really like someone to take this over and finish it up.  I just feel bad delaying this even more due to my schedule.  Any takers?</p>

<p>Thanks.</p>

<p>-Justin </p>

<p>Justin,</p>

<p>I have just created a proposal for Zend_Service_Amazon_Abstract so that all the Amazon Services can have the same key handling code.</p>

<p>After talking with a few people in the chat room i have moved this to a JIRA issue.</p>

<p><a class="external-link" href="http://framework.zend.com/issues/browse/ZF-5791">http://framework.zend.com/issues/browse/ZF-5791</a></p>

<p>Let me know what you think.</p>

<p>I have the unit test code done and checked into my sqs repo on gethub</p>

<p><a class="external-link" href="http://github.com/sidhighwind/zend_service_amazon_sqs/tree/master">http://github.com/sidhighwind/zend_service_amazon_sqs/tree/master</a></p>

<p>Jon</p>

<p>It would be nice, to add method like this:</p>

<p>getQueryString($object, $expire);</p>

<p>to return url like this:<br />
''http://bucket.s3.amazonaws.com/object?AWSAccessKeyId=44CF9590006BF252F707&Expires=1177363698&Signature=vjbyPxybdZaNmGa%2ByT272YEAiv4%3D''</p>

<p>or</p>

<p>''http://s3.amazonaws.com/bucket/object?AWSAccessKeyId=44CF9590006BF252F707&Expires=1177363698&Signature=vjbyPxybdZaNmGa%2ByT272YEAiv4%3D''</p>

<p>link to doc:<br />
<a href="http://docs.amazonwebservices.com/AmazonS3/latest/S3_QSAuth.html">http://docs.amazonwebservices.com/AmazonS3/latest/S3_QSAuth.html</a></p>

<p>pch</p>

<p>I have problem with upload big files to s3. Maybe good idea will be add method to do POST request?</p>

<ac:macro ac:name="note"><ac:parameter ac:name="title">Zend Comments</ac:parameter><ac:rich-text-body>
<p>This proposal has been approved for standard library.</p></ac:rich-text-body></ac:macro>