Posts tagged with: api

Links of interest for 5 Mar 2008 - 12 Mar 2008: iPhone rules pose Net neutrality, antitrust concerns - I just knew the iPhone SDK sounded too good to be true. It seems the license allows you to do "this", but not "that", nor "that", oh and "the other thing" isn't allowed either. Why release an SDK if you can't develop to your heart's content? I was really Snap Sun decision launches Java at iPhone - Cool. No hopefully people will start creating some useful Java apps for the iPhone (and other phones) and not just games. Acid3 Test Released... Continue reading ►

I've had a busy couple of afternoons quashing bugs and enhancing phpSmug further. This release sees the re-introduction of anonymous method call caching (Ticket #18), enableCache() now checks cache directory is writeable (Ticket #19), die_on_error is now acknowledged consistently. If die_on_error is NOT set, it's up to the application developer to check getErrorCode and getErrorMessage after each method call. (Ticket #20), I've added clearCache() function to easily empty the cache. (Ticket #22) and I've Stopped caching the results of failed method calls when die_on_error is set. (Ticket #23).

Fixed a tiny typo I made by including an extra "}" in phpSmug (line 203) (Ticket #17). This has been removed in phpSmug 1.0.9.

I've updated phpSmug to improve the caching and to take into account the SessionID 6 hour inactivity timeout after rolandk98 brought up a caching issue. I've also fixed a problem with escaping apostrophes when using a database for caching.

I forgot to take into account the ImageKey returned by image_upload() and image_uploadFromURL(), and AlbumKey returned by album_create(). As of rev 1.0.7/1.1.5, these functions now return an array holding the ID and key. Thanks to devbobo for pointing this out so quickly.

I've updated phpSmug to support the new security features introduced. You can find more details of the new security measures here.

I've been meaning to sort this out for ages, but completely forgot. Thankfully b-root reminded me by logging Ticket #14. phpSmug (as of rev 1.0.5 and 1.1.3) now uses SSL/HTTPS for all login.with* methods to ensure login information is not sent across the wire in the clear.

I've just updated the 1.0.x and 1.1.x branches of phpSmug to resolve 3 issues I discovered with the caching used by phpSmug (Tickets #11, #12 and #13)

I've updated the example.php file in the phpSmug 1.0.x to branch to take into account the "Heavy" argument. Whilst this isn't strictly needed in the example.php, it does cause confusion as it's the first parameter, and the example was only providing the nickname parameter. Thanks to Rob Nugen for the heads up on this. Ticket #9 is now resolved.

phpSmug 1.1.1, which adds support for rev 1.2.1 of the API, is now available. At the moment, it only officially implements those methods detailed at http://dgrin.com/showthread.php?t=71887. The code is in place for ALL of the functions listed on the wiki, however some of the methods haven't been implemented in the API itself, so I've not tested these, so can't be sure they'll return the correct data. At the moment, these methods are commented out and will return "Not implemented in API yet". I'll update phpSmug 1.1.x as these methods become available.