188660 - [CDE] Add support for CDE calendar server

Status: RESOLVED WONTFIX

(Calendar :: General, enhancement)

Description

[Roland Mainz]

RFE: Add support for CDE calendar server (see rpc.cmsd(1m) and csa/csa.h(5)
manual pages).

Comment 1

[Roland Mainz]

CDE calendar API description can be found under
http://docs.sun.com/db/doc/805-3910/6j3nbl4e9?q=csa&a=view

Comment 2

[Mike Potter]

Having a calendar server to be used for development would really help us develop
a solution.

Comment 3

[Roland Mainz]

Mike Potter wrote:
> Having a calendar server to be used for development would really help us 
> develop a solution.

Do you have a Sun/Solaris box around ?
If "yes", look for "rpc.cmsd":
-- snip --
% ps -ef | grep rpc.cmsd
  daemon   523   172  0   Dec 20 ?        0:07 rpc.cmsd
-- snip --
("rpc.cmsd" should be running by default, started by inetd (see
/etc/inet/inetd.conf ; enabled by default since (at least) Solaris 2.6)))

Comment 4

[Roland Mainz]

BTW: I was thinking about a way to _use_ the CDE calendar server (e.g.
read/write entries), not about an import function (that would be nice, too - but
being able to use the existing  (central!) rpc.cmsd servers from MozCalendar
looks like the more valueable feature for now).

Comment 5

[Mike Young]

The Penn State Mozilla Group will be taking on this bug as part of our project.
This should be completed by May 2003. Unfortunately, at the moment we only
forsee this working on Solaris as Sun doesn't distribute the necessary libraries
to connect to the server for other OSs. Once the code is complete, porting it to
other Unicies and then Win/Mac will be a seperate issue.

Any suggestions from more experienced Moz/Calendar hackers (esp Sun developers!)
would be greatly appreciated.

Comment 6

[Mike Young]

Attachment: Our design document for our class

We handed this design document in for our project, and wanted to post it here
in case anyone had suggestions.

We are in the process of developing a calendar server XPCOM component, and will
try to post that here soon. Our goal is to have a completely generic XPCOM
component so more servers than just CDE could use (and inherit from) it.
(Examples include Iplanet, SunOne, Netscape, X.400, CAP, etc.)

Comment 7

[Mike Potter]

Looks good to me, adding Mostafa to the CC list since he's written most, if not
all, of the backend code for the calendar so far.

Comment 8

[Penn State CSE420W Group]

Attachment: Our proposed idl interface (comments wanted)

mostafa, could you take a look at this and let us know if we're on the right
track?

Comment 9

[Mike Potter]

*** Bug 196396 has been marked as a duplicate of this bug. ***

Comment 10

[Grant Fengstad]

I believe that the Sun CDE API specification is somewhat different from their
new product API specification which has been shipped with the Sun ONE Calendar
Server.  The URL for this spec is http://docs.sun.com/source/816-6416-10/index.html

As the Sun ONE Calendar Server will be the strategic path forward, would it not
make sense to incorporate support for that server?

Comment 11

[Mike Young]

Attachment: Penn State's submision. This contains the mozilla/calendar directory, plus the other files we have changed

Here is our code. Please review :-)

Our deadline for code-review is April 24th. We would appreciate as much of a
review as you can in that time. 

This code is not yet ready to integrate with the trunk, as there are issues
with the OE Container.

Comment 12

[Mike Young]

Comment on attachment 120515 [details]
Penn State's submision. This contains the mozilla/calendar directory, plus the other files we have changed

attachment #120515 [details] is of type tar.bz2

Comment 13

[Mike Young]

Attachment: Documentation for more information about our patch

Comment 14

[Mike Potter]

I will give you approval on the XUL / JS changes that were made for this (which
aren't very many).  Good work guys (and gals?).

Comment 15

[Mike Young]

wow, sorry about the long delay with this bug.

We have gotten back together and up and running after the end of the school
year. There has been quite a bit of movement on this bug and the others that are
related but we haven't put most of it online because we've been out of our
regular meeting schedule at school.

Some of us are still students, and some of us have graduated and will be working
from whatever we are doing with our lives after college.

I plan on putting an update with our progress and a plan of what we are going to
be doing with the calendar to make it an all around better app. Look for it
coming soon.

Comment 16

[Mike Young]

Our plan has been posted. Please see the news posting at
news://news.mozilla.org:119/bhkmc2$[e-mail]
for more info, or see the following attachment.

Comment 17

[Mike Young]

Attachment: Development Plan

we'll be opening new blocking bugs with information on our Design and
interfaces as well as step-by-step tasks to reach the goal in this plan.

Comment 18

[Mike Young]

PSU is no longer funding students to work on mozilla :-(

The bugs we were working on (with the exception of bug 188660 are now irrelevant
with the massive backend changes that were made to the calendar.

I'm assigning this back to the general owner and QA of Calendar. Anyone who
wants to pick it up is welcome to do so.

In theory, with the new backend system, implementing this should be fairly easy.
(At least on solaris where you have a library to use)

Comment 19

[Matthew (lilmatt) Willis]

Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove

Comment 20

[Bas van den Bosch]

Does CDE-calendar still exist or is this wcap now?

Comment 21

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

I think we can safely WONTFIX this one.