I think I could've made that working on my own to. ;) But nevertheless,
those webform things do not have all the features I need.
Beside that: On my way to work I was just thinking about the factory pattern
we concidered to implement for SMS. The idea is quite cool, but the features
of the backend classes wil widly vary. So, how would you propose to deal
with that?
make the base class an abstract/factory - and just return PEAR::raiseError('Not supported'); by default..
from what I remember most of them do:
= construct 'driver', options
username/password/callcenter/from_number
- send sms
- send multimedia sms????
- get sms messages
of the top of my head.. I cant think of what else you would do with it
Regards
alan
Regards,
Toby
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com