Hi!
On 05/13/2008 04:51 PM Alexandru Stanoi wrote:
> Derick Rethans wrote:
>> On Tue, 13 May 2008, Alexandru Stanoi wrote:
>>> +Example of a new module type::
>>> +
>>> + class mySlashHandler extends ezcFeedModule
>>> + {
>>> + // schema which defines the elements (at feed and item level) used
>>> by this module
>>> + protected $schema = array(
>>> + 'feed' => array(),
>>> + 'item' => array( 'elementName' => array( '#' => 'string' ),
>>> + ) );
>> If we're exporting new stuff that defines a schema, we should definitely
>> come up with a different way of specifying it.
> Yes I think you are right.
> Does anybody have any ideas about how to define a feed type or a module
> without using big array structures, as they are used now in ezcFeedRss1,
> Rss2, Atom and ezcFeed*Module?
We use nested class structures in other components to describe schemas,
like in PersistentObject and Search. That way, you can perform sanity
checks on every level and therefore have a certain kind of security tha
the structure is correct.
Regards,
Toby
--
Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards
Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer
[EMAIL PROTECTED] | eZ Systems AS | ez.no
--
Components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/components
