You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Jeff Prickett <pr...@www1.kc.aoindustries.com> on 2002/02/23 05:31:21 UTC
Periodicity (iCalendar) Interest Survey
What is your name?
What is your email address?
What JDK version do you currently use for software development/deployment?
Are you interested in EJB support?
If so what J2EE version?
If so what EJB container?
What hardware platforms will you run Periodicity on?
What operating systems will you run Periodicity, please include version
numbers where applicable?
What database will you use to store the iCalendar objects, please include
version?
What features are you looking for from a calendar server?
Would you be willing to contribute time to help develop Periodicity?
Would you be willing to write documentation?
Would you be willing to write code to implement new features?
Would you be willing to submit patches to fix bugs?
Would you be willing to help others install, configure, and use
Periodicity?
What computer skills to you have?
What computer skills would you like to learn?
Have you contributed to Open Source before?
If so answer the following...
As a tester?
As a documentation writer?
As a developer?
As a technical support technician
Which projects?
If you have not contributed to Open Source in any of the above aspects
please answer the following question...
Is there anything we could do to encourage you to get involved in the
development of Periodicity or any other open source projects?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Periodicity (iCalendar) Interest Survey
Posted by Jeff Prickett <pr...@www1.kc.aoindustries.com>.
On Tue, 26 Feb 2002, dIon Gillard wrote:
> Jeff Prickett wrote:
<snip>
> Not really. Why would a calendar product *need* EJB support?
>
> >If so what J2EE version?
> >If so what EJB container?
> >
EJB support would be optional for those who would need it. We would
support a standalone version for people who just want a basic small scale
website/server and offer EJB for those who might need more scalability.
Note: I am not following the conversations about EJB on general (ok maybe
a little), but I find them highly irrelevant. When I first sent the email
about restarting iCalendar here at Apache it set off a flurry of emails
about Apache making an Exchange killer. I would like to see that happen
and I believe that if Periodicity is to become an Exchange killer we will
have to eventually support EJB, even if we dont think its the greatest
platform. Why? Because EJBs are widely accepted throughout the industry
and having an EJB version of Periodicity will make selling it to CTOs and
CIOs easier. Just my two cents
Bottom Line about EJB. To be accepted by the big corporations we may have
to wear a suit, even if it is uncomfortable.
> >What hardware platforms will you run Periodicity on?
> >
> All sorts. Intel, Sparc, RS/6000
>
Thanks, I hope that you will help us test on these platforms. We hope to
have a release out before the end of March.
> >What database will you use to store the iCalendar objects, please include
> >version?
> >
> Does it need a database? How about an XML format as an option (e.g.
> xcalendar?)
>
There actually is a dtd that was being maintained by the IETF, I believe,
it is an internet draft. The last one just expired Feb 18, 2002.
We will support this for of iCalendar also.
> >What features are you looking for from a calendar server?
> >
> Dunno yet. Interchange of cals between various platforms/products.
> Specifically Notes and vCal on Linux (korganizer).
>
This is exactly what iCalendar is about. The first release, maybe even the
first couple of releases wont support this, but we will.
> >Would you be willing to contribute time to help develop Periodicity?
> >
> Some.
>
Thanks for considering contributing and thanks for taking the time to
reply.
Jeff Prickett
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Periodicity (iCalendar) Interest Survey
Posted by dIon Gillard <di...@multitask.com.au>.
Jeff Prickett wrote:
>What is your name?
>
dIon
>
>
>What is your email address?
>
trongus@yahoo.com
>What JDK version do you currently use for software development/deployment?
>
JDK 1.4
>Are you interested in EJB support?
>
Not really. Why would a calendar product *need* EJB support?
>If so what J2EE version?
>If so what EJB container?
>
>What hardware platforms will you run Periodicity on?
>
All sorts. Intel, Sparc, RS/6000
>What operating systems will you run Periodicity, please include version
>numbers where applicable?
>
Windows 2k, Linux, Sol 8, AIX 4.3.x
>What database will you use to store the iCalendar objects, please include
>version?
>
Does it need a database? How about an XML format as an option (e.g.
xcalendar?)
>What features are you looking for from a calendar server?
>
Dunno yet. Interchange of cals between various platforms/products.
Specifically Notes and vCal on Linux (korganizer).
>Would you be willing to contribute time to help develop Periodicity?
>
Some.
>Would you be willing to write documentation?
>
Sure, if the itch was there.
>Would you be willing to write code to implement new features?
>
Sure, if the itch was there.
>Would you be willing to submit patches to fix bugs?
>
Sure, if the itch was there.
>Would you be willing to help others install, configure, and use
>Periodicity?
>
Sure.
>What computer skills to you have?
>
I know what one looks like....
>What computer skills would you like to learn?
>
>
>
>Have you contributed to Open Source before?
>If so answer the following...
>
Yes.
>As a tester?
>
Yes.
>As a documentation writer?
>
Yes.
>As a developer?
>
Yes.
>As a technical support technician
>
I suppose.
>Which projects?
>
Ant, Tomcat, Struts, Latka, HttpClient
>If you have not contributed to Open Source in any of the above aspects
>please answer the following question...
>
>Is there anything we could do to encourage you to get involved in the
>development of Periodicity or any other open source projects?
>
--
dIon Gillard, Multitask Consulting
http://www.multitask.com.au/developers
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: integrate security frameworks
Posted by Juozas Baliuka <ba...@centras.lt>.
Hi,
<skip>
> I've been expecting this conversation to find its way to
> commons sooner or later. I actually thought it might be
> me to start it. I think there is some simultaneous
> security wheel invention happening (maybe re-invention).
> Might be a good thing. I know at least Turbine and Avalon
> have been discussing JAAS independently.
Ok, it is very good. I think we don't need discuss a lot,
I think we must start project for LoginModule and Policy
implementations, we can implement it in simplestore, but
it is not very meaningful to have Policy implementation in this project,
it because Policy is singleton. We need common Policy implementation and
it must be possible to add plugins for it on runtime, to load permissions
from DB, XML ....
or grant some at runtime.
I think it must be very clear, we need proposal and VOTE to start this
project.
> I've hesitated
> to initiate this conversation 'cos I though it would
> degenerate into all the usual fire between Turbine, Struts,
> and Avalon, especially if the conversation is not focused
> on code. But here are some threads of which I am aware, in
> case it will help you.
>
> Turbine - start here and follow the thread
> <http://www.mail-archive.com/turbine-
> dev%40jakarta.apache.org/msg05759.html>
>
> Avalon
> <http://marc.theaimsgroup.com/?l=avalon-
> dev&w=2&r=1&s=AAA+implementation&q=b>
>
>
> Reading through the Avalon threads I was struck by how
> remarkably similar Avalon's conversation has been to
> Turbine's. Who would have thought? 8^)
>
> Good luck! It would be cool to find some common ground
> here. But I'll bet this one will get heated. 8^)
>
> -Eric
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
integrate security frameworks
Posted by Eric Dobbs <er...@dobbse.net>.
On Sunday, February 24, 2002, at 03:07 AM, Juozas Baliuka wrote:
> I will think abaut this, I want to review more jakarta code, and I
> think it
> is possible to
> integrate all security frameworks, to have the same authentication
> mechanizm
> and I it
> must not be any problems with authorization integration.
I've been expecting this conversation to find its way to
commons sooner or later. I actually thought it might be
me to start it. I think there is some simultaneous
security wheel invention happening (maybe re-invention).
Might be a good thing. I know at least Turbine and Avalon
have been discussing JAAS independently. I've hesitated
to initiate this conversation 'cos I though it would
degenerate into all the usual fire between Turbine, Struts,
and Avalon, especially if the conversation is not focused
on code. But here are some threads of which I am aware, in
case it will help you.
Turbine - start here and follow the thread
<http://www.mail-archive.com/turbine-
dev%40jakarta.apache.org/msg05759.html>
Avalon
<http://marc.theaimsgroup.com/?l=avalon-
dev&w=2&r=1&s=AAA+implementation&q=b>
Reading through the Avalon threads I was struck by how
remarkably similar Avalon's conversation has been to
Turbine's. Who would have thought? 8^)
Good luck! It would be cool to find some common ground
here. But I'll bet this one will get heated. 8^)
-Eric
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Periodicity (iCalendar) Interest Survey
Posted by Juozas Baliuka <ba...@centras.lt>.
<skip>
> Security is going to be JAAS based and that is one of the major areas
> still needing work before we can get a 0.0.1 release out the door. I would
> appreciate it if you would review my work so far and make some comments on
> what you think. I am new to JAAS and could use the feedback. Most of the
> new development with JAAS has to do with User and Group integration. We
> could, also, use some help with writing policy files and documenting how
> to securely configure Periodicity.
>
> If you would like to step up and help with JAAS integration with Turbine
> Users and groups it would be a great help to the project. Any help that
> you could offer would be appreciated.
>
> Thanks for your reply.
<skip>
Yes it is very interesting, I use JAAS and I think it is one of the best API
added
to JDK 1.4 . Simplestore was about cache or simple object storage bykey
only, but
it is becomes some framework for persitence, security and I have plans abaut
validation.
I know there area lot code this kind, and some of it is in jakarta. We must
think how
to reuse and integrate this code. JAAS is very good for security
integration, most of
projects have "user, group, role" and "some permission for some action".
I will think abaut this, I want to review more jakarta code, and I think it
is possible to
integrate all security frameworks, to have the same authentication mechanizm
and I it
must not be any problems with authorization integration.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Periodicity (iCalendar) Interest Survey
Posted by Jeff Prickett <pr...@www1.kc.aoindustries.com>.
On Sat, 23 Feb 2002, Juozas Baliuka wrote:
> Hi,
> I contribute for simplestore at this time, it is going to become some kind
> of "Transparent Persitence",
> we are going to implement some security, I understand, it is not some part
> of persitence.
> I see Periodicity is more abaut security, and I want to find some solution
> for integration.
> simplestore can be used for BMP, but not at this time, transactions are not
> portable at this
> time.
> I reviewed Periodicity, goals of project are not wery clear for me at this
> time.
> If it JAAS based security framework, I am going to spend more time for this
> project.
>
> <skip>
>
Jouzas,
The goal of Periodicity is to fully implement Internet RFCs 2445, 2446,
and 2447. These are the calendaring RFCs.
RFC 2445 iCalendar - Specifies what the data objects look like
RFC 2446 iTIP Transport Independent Interoperability Protocol - Specifies
how calendar servers should share, request, schedule, and delegate
calendar objects
RFC 2447 iMIP Message based Interoperability Protocol - Specifies how to
encode iCalendar objects into an email message.
In addition to implementing the RFCs we will be including a set of
Velocity templates for displaying and manipulating iCalendar data via a
Web Browser and Web enabled phone.
Security is going to be JAAS based and that is one of the major areas
still needing work before we can get a 0.0.1 release out the door. I would
appreciate it if you would review my work so far and make some comments on
what you think. I am new to JAAS and could use the feedback. Most of the
new development with JAAS has to do with User and Group integration. We
could, also, use some help with writing policy files and documenting how
to securely configure Periodicity.
If you would like to step up and help with JAAS integration with Turbine
Users and groups it would be a great help to the project. Any help that
you could offer would be appreciated.
Thanks for your reply.
Jeff Prickett
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Periodicity (iCalendar) Interest Survey
Posted by Juozas Baliuka <ba...@centras.lt>.
Hi,
I contribute for simplestore at this time, it is going to become some kind
of "Transparent Persitence",
we are going to implement some security, I understand, it is not some part
of persitence.
I see Periodicity is more abaut security, and I want to find some solution
for integration.
simplestore can be used for BMP, but not at this time, transactions are not
portable at this
time.
I reviewed Periodicity, goals of project are not wery clear for me at this
time.
If it JAAS based security framework, I am going to spend more time for this
project.
<skip>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>