So the plug-in should be able to consume and produce web feeds?
> Since the plug-in also handles atom feeds, should I rename the whole
> thing 'Web feeds'?
>
> Is it acceptable to refer to them all as RSS?
I don't think that code to do with atom should be referred to as RSS.
The best thing to do would be to create a "Web Feeds" plug-in that
contains some abstract classes. Code to do with Atom should be moved
to the "Atom Web Feeds" plug-in. The web feeds plug-in should contain
common functionality.
If some other format comes along, then we could start a new plug-in
that reuses the "Web Feeds" plug-in.
I'm not sure if everyone who uses RSS is going to need code that can
handle Atom and vice-versa.
Rob
> >
>
--
Rob Impey
>
> Since the plug-in also handles atom feeds, should I rename the whole
> thing 'Web feeds'?
Also, might "RSS Web Feeds" be a better name for the plug-in?
RFI
--
Rob Impey
OK, if it's just one class then there's no need to over-complicate
matters by separating the code into three plug-ins.
I wonder what the right time to separate code into new plug-ins is?
For one class, it seems like overkill.
Perhaps it's a mistake to look at this from the point of view of code
complexity or length. The question should be "Is it possible that a
programmer might not need this code?" If the answer is "Yes", then
that code should at least be considered for separatation.
Do you know of any other syndication formats that might be needed? If
there are a lot of them, then it might make sense to have one plug-in
for each. If it's just RSS and Atom, then a single plug-in probably
makes the most sense.
RFI
>
> --
> Saul
> >
>
--
Rob Impey