Re: GSM_SMS
| From: | Sterling Hughes | Date: | Thu, 09 Aug 2001 07:51:06 +0000 |
| Subject: | Re: GSM_SMS | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1322@lists.php.net to get a copy of this message | ||
On Wed, 8 Aug 2001, Mika Tuupola wrote:
>
>
> Earlier I mentioned about pearifying some PHP classes I have
> made for converting and sending operator logos, ringintones,
> textmessages etc. via kannel.
>
> I think the code for converting and sending the messages should
> be separated and atleast the latter abstracted for different
> bearers. The bearer code should allways have just one send()
> method which works with both binary and ascii messages without
> giving any other parameters than the message itself. The send
> method is different with every bearer because atleast binary
> messages are handled very different ways between the bearers.
> This might cause some bloating in the bearer code since it
> has to figure out what it is sending, but it will result
> as a simpler API.
>
> Below is some thoughs about the structure and usage (the
> original code was written before I found PEAR so it
> must be restructured). Comments and ideas are welcome.
>
>
> SmartMessaging/
>
> or
>
> GSM_SMS/
>
> or
>
> GSM/
> SMS.php
> SMS/
> OTA.php
> OTA/
> Bitmap.php
> Icon.php
> OperatorLogo.php
> RingingTone.php
> ...
> Bearer.php
> Bearer/
> Kannel.php
> SoneraCGW.php
>
Looks good, I'd use this structure.
-Sterling