NNTP design - factory pattern
From: Adie (usenet_at_dont-listen.net)
Date: 01/07/05
- Next message: Daniel Parker: "Re: What is an OODBMS?"
- Previous message: Thomas Gagne: "Re: What is an OODBMS?"
- Next in thread: H. S. Lahman: "Re: NNTP design - factory pattern"
- Reply: H. S. Lahman: "Re: NNTP design - factory pattern"
- Reply: Doc O'Leary: "Re: NNTP design - factory pattern"
- Reply: Marc Rohloff: "Re: NNTP design - factory pattern"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 07 Jan 2005 12:44:30 GMT
Hi, I've been away from writing code for a while and want to get back into
it (for fun).
Wanted to do some client/server programming, specifically NNTP and was
thinking about using the opportunity to learn more about patterns and
design.
My question is, as the NNTP protocol is already written, and set in stone,
should I base my OOD around the NNTP rules or should I abstract away from
it to what it's actually doing (if you know what I mean).
Also, when responses return from the server, they could be error messages,
no response, articles, lists of groups etc... I'd obviously like some
behaviour to recognise what they are and encapsulate them into whatever
type of object they should be, so might a factory fit this scenerio and if
so how might it look?
(Using C#)
Thanks for any comments.
- Next message: Daniel Parker: "Re: What is an OODBMS?"
- Previous message: Thomas Gagne: "Re: What is an OODBMS?"
- Next in thread: H. S. Lahman: "Re: NNTP design - factory pattern"
- Reply: H. S. Lahman: "Re: NNTP design - factory pattern"
- Reply: Doc O'Leary: "Re: NNTP design - factory pattern"
- Reply: Marc Rohloff: "Re: NNTP design - factory pattern"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|