FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » FUDforum » FUDforum Suggestions » NNTP Integration - use INN Storage API instead of MySQL
Show: Today's Messages :: Unread Messages :: Show Polls :: Message Navigator
| Subscribe to topic | Bookmark topic 
Switch to threaded view of this topic Create a new topic Submit Reply
NNTP Integration - use INN Storage API instead of MySQL [message #33293] Thu, 24 August 2006 04:57 Go to next message
woody is currently offline  woody   Switzerland
Messages: 19
Registered: August 2006
Karma: 0
Junior Member
add to buddy list
ignore all messages by this user
Hi All

Well, all those using FudForum as Web-Frontend for Newsgroup, probably have also a INN Server running on the same machine.

This means, the messages are storred twice. Once in the FudForum MySQL Database and once in the INN Database.

If FudForum would use the INN 'sm' (StorageManager) API, then you could save half the disk-space and it probably would also resolve all the problems about deleted messages not being deleted on the other storage and vice versa.

-Benoit-
Re: NNTP Integration - use INN Storage API instead of MySQL [message #33296 is a reply to message #33293] Thu, 24 August 2006 11:13 Go to previous message
Ilia is currently offline  Ilia   Canada
Messages: 13241
Registered: January 2002
Karma: 0
Senior Member
Administrator
Core Developer
add to buddy list
ignore all messages by this user
FUDforum needs to have its own message storage otherwise things become very tricky and subsequently slow. In FUDforum the message text may also be altered by import regex or language filters, so a dedicated copy is essential.

FUDforum Core Developer
Quick Reply
Formatting Tools:   
  Switch to threaded view of this topic Create a new topic
Previous Topic: BugReport: IPv6 addresses being truncated
Next Topic: NNTP Integration - Crontab simplifying.
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Dec 14 12:18:49 EST 2017

Total time taken to generate the page: 0.00568 seconds