Re: [Agendaware-dev-client] Dev Question

[Shane T. <tur...@ya...>]

Good point, I'd forgotten about the other comms we may need
to implement later.  I think we can still make a standard interface
for the client to use though, we just need to put a little more design
thought into it.  I'm thinking maybe we can implement some sort
of set of common "interface" classes (Java terminology) that encapsulate
the API's that the client will use, and then we can have each specific
communication module implement that API, so there is not a major
changing of client code when adding other things such as IMAP, POP, LDAP.

How about we brainstorm on a few design ideas and we'll see what we can
come up with?  The overall goal should be that adding additional "server
comms" should be almost transparent to upper level client code.  We can
make it "pluggable"(like the client loading the appropriate libraries at
run time) and then any one could make a java module (if that's what you
want to call it) to connect to his/her own mail server, directory server,
etc . . .)  I think this would be a very cool feature for
integrating with other groupware servers.

Just drop a line with any ideas you have . . .  I'll do the same
when I come up with something  . . .

Thanks!
Shane
 
--- Joerg Althoff <joe...@gm...> wrote:
> Am Donnerstag, 25. April 2002 03:51 schrieben Sie:
> 
> >
> >     Directory Services | Mail | Calendar | Admin
> > -------------------------------------------------------------
> >     DirComms  |  Mail Comms |  Calendar Comms | Admin Comms
> >
> > (Another reason is that I'm getting a craving to do some Java
> > and thought this would be a good way)  :-)
> >
> > How does this sound guys???
> >
> Hi Shane,
> 
> sounds good. As I understand, you want to create some Java Classes with
> all 
> the XML Stuff for server communications build in. 
> 
> This classes have well defined interfaces, like 
> serverAdminComms.logon(userid) or 
> serverCalendarComms.getCalendarEntriesVetcor() or 
> serverMailComms.getMailMessagesVector(mailbox).
> 
> But there is one thing to think about. As I understand the goals of the 
> client, the AgendServer will not the only source of information for the 
> client (Zack????). POP3, IMAP, ICQ, LDAP??, and so on. 
> 
> The status now is:
> 1. Reading and writing data to the local client store
> 2. Logon to the AgendaServer
> 3. Presentation of mail data
> 
> If we want to reach the other servers we have to design such an
> interface for 
> the client side, in wich we can plug in several modules for server 
> communication (not only for AgendaServer, but also for POP3 server, and
> so on)
> 
> 
> Greetings Joerg
> 
> 
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/