> probably need to use the a resource loader to load up a properties file,
> along with the text for footers and headers.
Noooooooo! LOL
You really want to separate content from mechanism. What if someone wants
to integrate mailing lists with a web community? Are you going to have one
set of information stored in properties files, and related (possibly
redundant) information stored in a database?
I don't want to store things in properties files. I want them organized in
a maintainable database. I want model objects that I can use from an SMTP
mailet, web service, JMX plug-in, or other web entity to modify the
configuration of my mailing lists. YMMV. That is why data modeling and
separating content from storage mechanism is important.
--- Noel
-----Original Message-----
From: Brian 'Bex' Huff [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 03, 2002 13:31
To: [EMAIL PROTECTED]
Subject: RE: Digest listserv
yeah... all that stuff is pretty important as well... there's probably
too much configuration involved to put in the XML Mailet config space...
probably need to use the a resource loader to load up a properties file,
along with the text for footers and headers.
Im curious to see what mailets people have already... mailet.org pretty
much just has a "coming soon" page... where are people trading code in
the interim? Id be happy to share mine... once it actually works ;)
--
Brian 'Bex' Huff
[EMAIL PROTECTED]
Phone: 952-903-2023
Fax: 952-829-5424
>> has anybody out there written a ListServ mailet that does digests?
>
> Not yet, but I'd be interested to see one.
>
> Right now we have a few disjoint items that don't work well together.
What
> we really should do is to coalesce the various listserv related items into
> one uniform set, rather than create even more items.
>
> Feaures required:
>
> - dynamic list management that is complete data driven
> - opt-in confirmation
> - digests
> - finer control over attachments
> - footer support
> - ...
>
> How many are on your list? :-)
>
> --- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
