Server / API / Application type code?
| From: | Joe Stump | Date: | Mon, 02 Jun 2008 03:17:20 +0000 |
| Subject: | Server / API / Application type code? | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-50213@lists.php.net to get a copy of this message | ||
So I've been thinking about creating a web service frontend for Gearman that'd, essentially, allow you to post some JSON to an HTTP URI and it'd fire off a background job for you. It's similar to what the PEAR channel server code would be in that you'd do something like:
<?php
require_once 'Net/Gearman/WebInterface.php';
Net_Gearman_WebInterface::run();
?>
And then you'd post to that and it'd handle everything from there. My questions are:
1.) Is this type of application code allowed in PEAR (it has a fuzzy history I think)?
2.) Are there any established naming conventions for such things?
3.) If the answers are yes to 1 and no to 2 then what would people suggest for conventions?
Thanks!
--Joe