How about requiring that <tip> and </tip> be on lines by themselves? Or at least that <tip> has to be at the beginning on a line. Then you wouldn't have to worry about commented tips, and you probably should ignore them anyway, because the original message would have gotten the tip parsed out already.
Also, how about rewriting the <tip> tag with an id attribute when you process it. Then if you find the tip again with a matching ID, you can check the contents against the DB and either ignore or update, rather than inserting again. That'd be helpful for typo correction and/or evolving examples. cheers, barneyb On 9/29/05, Michael Dinowitz <[EMAIL PROTECTED]> wrote: > Once some side issues are dealt with, I'll have all of the tips loaded into > its own table and then into its own feed. The side issues include multiple > tips per post, commented tips, duplicate tips, etc. A possible solution is > to remove, comment or alter the tip container tags when a tip has been saved > to the DB. Another is to code a recognition into the system for a tip which > starts on a commented line that may span multiple lines. The problem with > that is some people don't have brackets to delineate a commented line and > others put in their own, non-standard comment characters. I'll get a solid > solution and implement it. > > There's always more to a feature than the feature itself. :) > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:219668 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
