Yes, that is correct.  I suppose it can easily be likened to a text
message, except there's no fee associated with it (other than the
immediate and upfront purchase of the application to run on the
phone).  There are 3 fields that (can) get sent to the device:
Application Name, Event, and Description.  It could be something like
"CakePHP Unofficial Forums", "A reply to your topic has been made",
"In order to solve the problem you're having with the AppController,
you'd want to make sure to......" (the description field can contain
10000 characters).

Really, the actual solution of how it's used or what's sent is up to
the developer.  It might be more interesting for you personally if it
sent messages on new account signups, but it might also be of value to
visitors of your site that own a capable device.  I'm stuck on how
developers might want to access or use it.  I see little value in
releasing a plugin if developers would need to further tweak it to
make it work the way they want.  That's where my problem is.  :)  For
another example of how Prowl was used (in conjunction with Growl) in a
business setting: http://ex-libris.ca/?s=prowl - although it uses
Growl, it could just as easily use a web API.

As an aside: from what I've read, the author of Prowl intends to
eventually extend support for other phone brands, but there's no
timeframe for that.  I don't own an iPhone either, but I have an iPod
touch so that I can get all of the same functionality.  ;)


On Jan 8, 10:53 pm, euromark <[email protected]> wrote:
> looks really interesting!
> if only i had an iphone... :(
>
> did i get this right - via API you can send notifications to your
> mobile?
> like if somebody new registers on your website etc?
>
> On 8 Jan., 21:19, BrendonKoz <[email protected]> wrote:
>
>
>
> > I've recently discovered Prowl (http://prowl.weks.net/) for the iPhone/
> > iPod touch.  It's basically an alerting system that sends Push
> > notifications to your device for certain actions.  It can integrate
> > with Growl for Windows or OSX, but more importantly (in this case), it
> > offers up an API.
>
> > I've used the API to create a datasource (before realizing there have
> > been others who've created 
> > components:http://projects.ofjacob.com/cakephp-prowl-component/
> > andhttp://thewebandthings.synodicsolutions.com/2009/08/06/introducing-th...).
> > Regardless of this fact, there still exists the ability to incorporate
> > more features out of the box than simply a call to a component within
> > a controller.
>
> > Here's what I need help with conceptually:
> >  - What feature(s) would you like to have in such a plugin (assuming
> > this would be useful to you)?
Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en

Reply via email to