[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: A new framework for embedding ... without CORBA
From:       Dawit Alemayehu <adawit () earthlink ! net>
Date:       1999-10-02 1:30:08
[Download RAW message or body]

On Fri, 01 Oct 1999, Graham TerMarsch wrote:
> Kurt Granroth wrote:
> > Graham TerMarsch wrote:
> > > I'd looked at what'd really be involved in doing one, and didn't think that
> > > it'd be too hard to do.
> > 
> > Nope!  The ioslave part is a piece o' cake as long as you know the
> > protocol itself.
> 
> Oh, I've gotten pretty good at working with it (again) as at the moment I'm
> doing all of the NNTP stuff manually as I've needed to do things slightly
> differently than I'd seen in other NNTP modules we've got in CVS.  Would there
> be any one in particular that you'd recommend looking at as a reference?
> 
> > > However, I did have question as to how NNTP URLs would be
> > > represented, considering that NNTP itself has several other
> > > extensions (e.g. 'xpat') that don't really map across into any sort
> > > of URL.  Other things such as "how do I just pull down the _headers_
> > > for a single msg, without the msg body" also left me as a bit
> > > puzzled as to how they'd map properly.
> > 
> > You will need to use a kioslave specific URL in this case.  The
> > problem (as you well know) is that all "official" NNTP URLs don't
> > contain nearly enough information.
> 
> I know, that's why I was left puzzled with the "how the heck do I make it
> do..." type stuff.
> 
> > You might want to try something like:
> > 
> > nntp://user:pass@host:port/news/path/msg?action=something&other=action
> > 
> > Some *possible* examples
> [.....snip.....]
> > 
> > Formatting the URLs like this makes parsing quite easy and one can
> > contain a LOT of information in the x=x pairs (all started with ? and
> > seperated by &)
> 
> You rock.  I'd known that this sort of stuff was "possible", but wasn't sure
> if it'd be acceptable to put any of it in there.  Perhaps I'll run along here
> and build something up that I can let others have a gander at and we'll see
> how it comes together from there.

I do not mind taking a look at once you have something.  I have a question
though.  Are you going to support both USENET url formats as specified by
RFC 1738, "nntp" and "news" ?

Regards,
Dawit A.

[prev in list] [next in list] [prev in thread] [next in thread]