From: Mike N. <mh...@us...> - 2005-05-03 16:40:57
|
On Tue, 2005-05-03 at 08:52, Shaun Murray wrote: > On 3 May 2005, at 16:39, Mike Noyes wrote: > > Personally, I prefer an NNTP client. HTML isn't designed for > > discussion. > > That's mixing how discussions are stored with how they are displayed > really. I've no objections to storing comments in an NNTP store but > ultimately you still have to display them in HTML and allow people to > discuss using a web browser interface. Shaun, I indicated a preference for NNTP client over an HTML browser. Both are clients for display/interaction. > Allowing access via an NNTP > client directly is nice too although commercially it would be a > disaster for some sites allowing users to bypass any revenue > generating adverts or content. I submitted this SF RFE a while ago to address that very issue. NNTP PHP Web Interface https://sourceforge.net/support/tracker.php?aid=1072029 > NNTP clients make threaded discussion viable because they run fast > and native on the client OS. That's tricky to do in a web browser > unless you implement it with XMLHttpRequest and Javascript aka AJAX > otherwise you've got multiple page reloads when navigating threads. Correct. It's a big waste of bandwidth, and a kludge. Unfortunately, NNTP got a bad reputation from USENET. :-( > There's certainly more we could do to open up the interfaces in > phpWebSite to other protocols other than HTTP, such as Atom, XML-RPC > or NNTP but at the heart of it you've got to have a good browser side > experience. Agreed. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs |