agendaware-dev-server Mailing List for Agendaware
Status: Inactive
Brought to you by:
zacklink
Menu
▾
▴
agendaware-dev-server — Dev List for Server development
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(33) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(10) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rahul K. <ag...@my...> - 2006-03-26 08:55:37
|
Greetings Everyone, How are you all ? It has been a long time we touched base. I hope you all had a wonderful life during these days. The world has changed in 5 years since this project was started. We all left it in between, but the project suerly had all the ingredients for success. Any one still willing to work on making it see light of the day ? Best Wishes, Thanks, Rahul |
|
From: Shane T. <tur...@ya...> - 2002-05-12 05:43:03
|
Hey everyone, Just posted the new server stuff with directory services. There are api examples under the "api_examples" directory. Let me know if you have any problems with it or if you encounter a bug that you can't get a around and i'll try and fix it as quick as I can to get you back going again. About to get my internet connection restored to my home linux box so maybe updates will come a little more frequently in the future. Next, I'm going to look at the connection handling stuff and make it a little more robust than it is now. May do a little perf stuff just to see how it stands up under a moderate load. Also looking into how to integrate external email into the server also. Trying to find some good external libs for parsing mail messages and such (if anybody has any ideas, let me know). If there's some other features you'd like to add sooner, let me know and we'll see what we can do. Have fun! Shane __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com |
|
From: Zack L. <za...@th...> - 2002-05-02 01:10:44
|
Hey All, Joerg has agreed to take over management of the client side. He is very good at what he does, and I trust he will do a great job. So, thanks from me Joerg and good luck! Probably the best thing for everyone who is contributing on the client side, or wants to, is send Joerg an email, so he can coordinate the development. Thanks everyone for contributing and participating, it is much appreciated. Zack |
|
From: Zack L. <za...@th...> - 2002-04-27 02:29:15
|
I have been dreading sending this email for the past couple of weeks, but it has become evident to me that I can no longer manage this project. Work is taking up more and more of my time, and I just can't do a decent job on Agenda. So, I am passing the torch. Really two torches as I think the 2 things I do are seperate. There is the client-side manager, and the overall project manager. While the overall project manager title hasn't meant much extra work, as Shane has done such a great job managing (and coding too ;-) ) the server side, it hasn't needed any. I am hoping that Shane will take over as the overall project manager, because I think he will do a better job than I can. That still leaves the client side manager. I would prefer someone who is already contributing, if nobody suitable volunteers, I will go ahead and post a job on sourceforge. And again, I really love this project, and hope it goes far, but I am just spread too thin now. I also want to thank everyone who has contributed to the project. You guys are what has made this happen, and I appreciate it. I have learned things from every one of you. Thanks, Zack |
|
From: Shane T. <tur...@ya...> - 2002-04-25 01:53:05
|
Hey guys, just had an idea and wanted run it by you.
Currently when developing the server, I'm continually testing
the XML comms to insure that I didn't break anything, etc . .
I was wondering if anyone would object to the server side
also maintaining the Java side of the communications stuff.
Not everything, just mainly the code dealing with generating,
receiving and decoding the XML communcations. (Right now, it
would by the CommsParser class that's defined on the client side)
This would also help me as while I was writing the server and developing
the comms, I could update the Java side comms to match and then use those
to do my testing and insure that the testing programs I'm using (that are
written with the Java comms) would be re-used by the client code.
I'm thinking that if we decide to do this, we could create some well
defined interfaces/classes to be used by the client and as along as
the interfaces remain constant the client could be shielded from the
communications side as long as the server side keeps the comms current.
(With, of course, suggestions or additions for client guys).
Also, while I was prototyping some stuff for an admin GUI, I started
thinking that I would want to reuse the comms stuff you guys had
instead of creating my own.
Thinking it would look something like this, where the
horizontal lines represent the insulating layers between
the interfaces. Client would use/maintain the top layer,
and server would maintain the bottom layer.
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???
__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/
|
|
From: Shane T. <tur...@ya...> - 2002-04-22 21:38:39
|
Thanks for the pat on the back! There will be one last update for the server and that will be minor directory services that I mentioned in the previous email. Everything is working now, just some more testing to be done before I commit the change. The changes will be: -- Directory service -- lookup up user based on directory id -- directory searching capabilities on first or last name (based on wildcards) . -- when adding a user to the server, also adding their directory entry so they can be looked up by the client. -- This should allow for fully functional directory and mail services within the registered agenda users on the server(nothing external working yet). After these are in, we'll stop on the api stuff and let the client get in sync and make sure they both talk the same language. I'm also starting to prototype an admin gui for administration purposes. While you guys are syncing up the client with the server, I may toy around with the connection handling and such (maybe look at performance, connection management, etc . . .) BTW, the API seems to be diverting somewhat from the original draft out there, so the best bet at this point is to use the command line utilties and figure out what output is being received and then code the GUI appropriately. There's an "api_examples" directory where I'm storing the format of the XML commands that can be issued and should be the correct syntax that the server understands. I'll let you know when I get this last drop of code in . . . --- Agyani <ag...@my...> wrote: > Hello, > > "Hat's off " to Shane's dedication and commitment, with development gone > dead he is still on and working to make agendaware server see light of > the day. > > Well to appreciate his effort and dedication I have started work on > adding database support using Postgres. Core classes are ready and work > is on at full swing, soon we may have db support. > > It is now time to wait and synchronize the client with the server to > make both of them talk and start using the new functionality of the > server. > > I admit that my contribution has not been much lately, due to work and > study pressures. But now as things have stabilized a bit, I would try to > be more active. > > Lets all of us come back and start the game again with new sprit. > > regards, > > Rahul > > __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ |
|
From: Agyani <ag...@my...> - 2002-04-22 18:14:12
|
Hello, "Hat's off " to Shane's dedication and commitment, with development gone = dead he is still on and working to make agendaware server see light of = the day. Well to appreciate his effort and dedication I have started work on = adding database support using Postgres. Core classes are ready and work = is on at full swing, soon we may have db support. It is now time to wait and synchronize the client with the server to = make both of them talk and start using the new functionality of the = server. I admit that my contribution has not been much lately, due to work and = study pressures. But now as things have stabilized a bit, I would try to = be more active. Lets all of us come back and start the game again with new sprit. regards, Rahul |
|
From: Shane T. <tur...@ya...> - 2002-04-15 04:29:02
|
Hey everybody,
Just wanted to let everyone know that I have made some progress
on the server side (not checked in yet). Currently I have directory
services basically working such that you can request a directory
entry given you know the specific directory id. Now I'm adding
some indexes and searching capabilities so that the client
can query for a specific user given a search string such
as "???rge" or "*rge" (? matches 1 char and * matches 1 or more)
The above two strings would both match an entry for "George" for instance.
Sorry for the hiatus, but work has been a bit intense here lately
and hopefully is beginning to settle down.
Once we get directory stuff working, does anybody have any preference
on what area we start on next? Below are listed a few of the areas
that need to be dealt with in the immediate future
-- personal address books (currently dir services work with other people
that have agenda logins)
-- server to deliver and accept "external" email
-- add user preferences storage/retrieval to server
-- retrieve/store folders on server
-- any other suggestions
Let me know what you would like.
How's everybody else doing . . . ?
Shane
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
|
|
From: Zack L. <za...@th...> - 2002-03-22 03:17:46
|
Cool. As far as my progress, I am going to get the client and server comms synced up. Will start working on that soon. What is everyone else working on now? Zack Shane Turner wrote: > The api for retrieving messages now works correctly when specifying > "last_check_time". If the value is 0, it retrieve all messages, otherwise > the value should represent number of seconds since epoch. This is then > used to search for all messages later than the corresponding date. > Also directory services are in progress and hopefully have something > in a week or two. > > How's everybody else doing? > > Shane > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ > > _______________________________________________ > Agendaware-dev-server mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-server > > > |
|
From: Shane T. <tur...@ya...> - 2002-03-17 21:48:32
|
The api for retrieving messages now works correctly when specifying "last_check_time". If the value is 0, it retrieve all messages, otherwise the value should represent number of seconds since epoch. This is then used to search for all messages later than the corresponding date. Also directory services are in progress and hopefully have something in a week or two. How's everybody else doing? Shane __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ |
|
From: Shane T. <tur...@ya...> - 2002-02-13 20:47:05
|
Have any of you looked at this? Kinda scary, but I don't know if it's a big deal or not. http://slashdot.org/article.pl?sid=02/02/13/188234&mode=thread&tid=150 __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
|
From: Shane T. <tur...@ya...> - 2002-02-11 03:14:21
|
The new server is out there now. It now has mail support. There are a few things to mention before running though. Adding a mailbox is used through a separate utility for now (mailAdmin). This is in the RUN_INSTRUCTIONS. Also, the server now validates the user and password. It validates that a mailbox exists for the user, so be sure to run the mailAdmin utility to create a mailbox to login to. Also, it accepts any password except the word "password". I just put this in so the client can emulate a failed login. Also, the last_check attribute of the RetrieveMailMessageRequest is used, however it always returns all messages and not just the ones from the given time period forward. I'll update this a little later. Next focus is on direcotry services (and any problems you guys find interacting with the client and server). Have fun! __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
|
From: zack <za...@th...> - 2002-02-07 02:36:48
|
Just read the server update. Moving right along, very cool. On the last_check_time mentioned below, I think we do need it for 2 reasons... 1) If the user moves from 1 box to another, the user would only get messages not downloaded on their other machine. POP3 has similar issues. With last_time_check, it will be much easier for the client to check the local db and sync just what it needs. 2) In case of the client detecting some internal inconsistency, it will have more power itself to recover from data integrity problems, while still minimizing bandwidth, responsiveness and server load. The client should be able to get up to speed on the comms pretty quickly, in fact, if no one else is working on it, I will do some work on that soon. Thanks, Zack Shane Turner wrote: > Just some thoughts regarding APIS. I've run into a few areas where it > seems the APIs don't make much sense so I wanted to get some feedback. > The main one I wanted to ask about was the RetrieveMailRequest. > It currently looks like this. > > <RetrieveMailRequest mailbox="xxx" request_id="xxx" format="header" > last_check_time="xxx"/> > > Where last_check_time is used to indicate a timestamp of the last time > the client checked for messages. I was thinking that the server ought > to be able to know what new messages have been delivered but haven't been > requested by the client so I was wondering if maybe we should change > last_check_time to something like "type" where the applicable values > would be "all" meaning to retrieve all messages and "new" meaning to only > give back new messages. last_check_time just doesn't seem appropriate. > > What do you guys think? > > Next, I was looking at the client code and it doesn't look like we're in > sync with the APIs with respect to responses and such. Just as a helper, > when I get the next version of the server out, I'm going to send small > command line programs that can be used to connect to the server and view > the different responses. I'll also include the exact APIs that the server > understands then you guys can let me know if there's things I need to > change or if you agree with the state of the APIs. > > Any problems or questions? > > > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com > > _______________________________________________ > Agendaware-dev-client mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-client > > > |
|
From: Shane T. <tur...@ya...> - 2002-02-06 17:55:46
|
Just some thoughts regarding APIS. I've run into a few areas where it seems the APIs don't make much sense so I wanted to get some feedback. The main one I wanted to ask about was the RetrieveMailRequest. It currently looks like this. <RetrieveMailRequest mailbox="xxx" request_id="xxx" format="header" last_check_time="xxx"/> Where last_check_time is used to indicate a timestamp of the last time the client checked for messages. I was thinking that the server ought to be able to know what new messages have been delivered but haven't been requested by the client so I was wondering if maybe we should change last_check_time to something like "type" where the applicable values would be "all" meaning to retrieve all messages and "new" meaning to only give back new messages. last_check_time just doesn't seem appropriate. What do you guys think? Next, I was looking at the client code and it doesn't look like we're in sync with the APIs with respect to responses and such. Just as a helper, when I get the next version of the server out, I'm going to send small command line programs that can be used to connect to the server and view the different responses. I'll also include the exact APIs that the server understands then you guys can let me know if there's things I need to change or if you agree with the state of the APIs. Any problems or questions? __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
|
From: Shane T. <tur...@ya...> - 2002-02-05 23:37:09
|
One other thing. In the original design diagrams, it shows a cache layer between the storage layer and other layers. This is going to change. The storage APIs will be accessed directly and it will be up to the person implementing the storage layer to implement their own caching techniques. This seems to be cleaner. I'm thinking one might have more control of performance if they're able to create their own caching strategy when they implement a type of storage. Anyone see any problems with this? Note: forwarded message attached. __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
|
From: Shane T. <tur...@ya...> - 2002-02-05 23:24:15
|
UPDATE: Mail on the server is almost finished. Rahul has implemented the SSL stuff and things look good. Currently, the storage API's are changing quite a bit from the design doc and these changes come and I get closer and closer to getting mail in place (and thus find holes in the API). I think for now, we don't need to jump on the DB storage because of this, however I think we can still go forward with the generic database abstraction layer. There should be no ties from the abstraction layer to the storage API's anyway. Rahul, do you plan on working more on the server or client? I have had a few responses from other people wanting to work on the project and if you were migrating to the client, I was going to hand the db abstraction layer off to someone else. If you're doing mostly server stuff, I'll try to find something else for them to work on. Thanks! Shane Happy Coding!!! __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
|
From: Shane T. <tur...@ya...> - 2002-02-03 19:48:53
|
Hey Rahul, code looks good. thanks! Everyone, Mail is almost there. Messages can currently be sent and received from the server. Just have to add delete and update. Then run it through a few tests. Things got a little delayed because I got hung up with the app seg faulting, but I think I've got that under control. I'm on vacation for next 3 days so hopefully I'll get some work done and get this thing out. Happy coding! --- Agyani <ag...@my...> wrote: > hi dev team, > > updated server for ssl related changes. plz read BUILDING for new chages > to the building structure of the server. > > may u have an error free compile :-) > > rahul > __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com |
|
From: Agyani <ag...@my...> - 2002-02-03 15:57:48
|
hi dev team, updated server for ssl related changes. plz read BUILDING for new chages = to the building structure of the server. may u have an error free compile :-) rahul |
|
From: Agyani <ag...@my...> - 2002-01-31 21:09:26
|
hi, SSL on server done. Changes to be uploaded on weekend. Methodology followed SecureSocket extends StandardSocket overriding read,write,accept and = connect methods SecureSocket takes a path to cert file(pem format) in constructor, = initializes ssl context and adds the file to its store. Server does not do any kind of client verification, it only presents the = client with its certificate now its up to the client to connect or not. SecureSocket is so made to accept both SSLv2 and SSLv3 connections. Tests have been conducted for both client and server model of = securesocket. Server was test with a java client having server's cert in its keystore. if any changes required to the above scheme mail me. rahul |
|
From: zack <za...@th...> - 2002-01-29 02:50:40
|
Hey everyone, We now have 9 people working on this project! I think this mean we should start moving along pretty quickly and get some good momentum. It also means that we need to organize a bit better because we don't want everyone working on the same things. So, I think we should start using the task manager in sourceforge so that everyone knows what everyone else is working on. Basically, if everyone could take a look at the task list, and add a task for everything you are working on. This should make things a bit more organized. And if any task is doubled up on, we can sort it out. Task List is here... http://sourceforge.net/pm/?group_id=38229 Thanks, Zack PS - We all should have rights to add/modify tasks, so if anyone can't, send me an email and I will correct it. |
|
From: zack <za...@th...> - 2002-01-29 00:41:30
|
I am back. I have been working with Hans on local data storage (LocalStore) and the mail message data model, client<-->server comms, as well as some event handling (popup menus etc). ZL Shane Turner wrote: > Could everyone take a minute to response to all on this email and indicate > what parts of the project you are currently working on or plan to work on > in the near future? We have some people answering our requests for some > help, but we need to know exactly who's working on what and then fill in > the holes. So everyone take a minute to jot down what you're doing or > plan on doing. > > Thanks! > Shane > > FYI, I'm currently working on the server for mail delivery as well > as directory support. Once mail is working, I'll move on to directory > support, then probably enhance the two. After that, I think calendaring > will be the next move. > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ > > _______________________________________________ > Agendaware-dev-server mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-server > > > |
|
From: zack <za...@th...> - 2002-01-28 01:09:20
|
Hey everyone, I was out of town, and just got back. I will respond to any emails tonight or more likely tomorrow. Zack Shane Turner wrote: > Could everyone take a minute to response to all on this email and indicate > what parts of the project you are currently working on or plan to work on > in the near future? We have some people answering our requests for some > help, but we need to know exactly who's working on what and then fill in > the holes. So everyone take a minute to jot down what you're doing or > plan on doing. > > Thanks! > Shane > > FYI, I'm currently working on the server for mail delivery as well > as directory support. Once mail is working, I'll move on to directory > support, then probably enhance the two. After that, I think calendaring > will be the next move. > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ > > _______________________________________________ > Agendaware-dev-server mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-server > > > |
|
From: Agyani <ag...@my...> - 2002-01-23 17:16:10
|
FYI,I'm currently working on SSL on both client and server and plan to = move on to add database supoort. I'm also working on the client to add = storage/reterival of user prefferences. |
|
From: Shane T. <tur...@ya...> - 2002-01-22 21:36:06
|
Could everyone take a minute to response to all on this email and indicate what parts of the project you are currently working on or plan to work on in the near future? We have some people answering our requests for some help, but we need to know exactly who's working on what and then fill in the holes. So everyone take a minute to jot down what you're doing or plan on doing. Thanks! Shane FYI, I'm currently working on the server for mail delivery as well as directory support. Once mail is working, I'll move on to directory support, then probably enhance the two. After that, I think calendaring will be the next move. __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ |
|
From: zack <za...@th...> - 2002-01-20 18:15:30
|
I agree with all the ideas below, and have added some additional comments inline. ZL Shane Turner wrote: > Since the compile farm is down, I thought I would take the time > to consider some other options that we may want to add in the future. > > First off, once I get mail support in place, it shouldn't take long > to get simple directory access in order since I have a lot of useful > stuff from getting the mail api together. > > Also, I was thinking of some of the exact preferences that we may > want and I thought I would throw out a few ideas. You may > have already thought of some, but hopefully i've come up with > some that you haven't. > -- Away Message and indication of when to use (user is away) Yeah. I think this could be just another filter. Maybe the user interface for doing an "out of office" could be different than a normal filter, in which certain assumptions are made, or building a specific dialog, just for out of office. But the underlying mechanism, could just be a filter. > -- Language (this is an example in the design docs) > -- Save copy of sent mail (yes or no) > -- How often to check for new mail(or only when explicitly done by user) > and type of notification (audible or visual, etc. .) > -- Maybe other mailboxes to make available to access with quick links > other than local mailbox. > -- Maybe allow access to other POP and IMAP accounts/mail servers from > client. This shouldn't be too hard with the Java Mail API. > -- Use trash folder for deletion or immediately delete. > -- Lock client after period of inactivity (request password to restart) > -- Client probably needs a local archive location to pull down > mail and move it off the server before it's automatically deleted > (if configured to do so). > -- User may configure scheduled archiving. Maybe through script like > interface I mentioned above. All good ideas. > > Things we may want to add in future . . . > > -- Some sort of option for users to add maybe custom filters and such > so that they can for instance to say "if mail message subject contains > 'meeting' send to trash'". I don't know if this will involve > some sort of mini script or something or what, but if you're willing, > I am. I think filters should be used on the server. The user builds a set of rules, and the filter is saved in a table in the server database. That seems to me like the only way a filter can be processed if the user is not logged in. The server will have to go through the filters table, as it is processing mail. The other option is to use filters on the client side (but out of office will have to implemented seperately, on the server). This, I think is a more complicated solution (because out of office would be seperate), but might be required to take some load off the server. I honestly haven't thought about this a whole lot, so if someone can see some pros/cons with either method, please respond. > -- A stationery option. > -- Maybe some sort of minimal document store, nothing major like lotus > notes, just simple documents with simple Id's. This may be extremely > long term and it's always possible I'll change my mind about this in > the > future. I agree. I have been hoping for a threaded bulletin board-like feature. These could be for company/division/workgroup type posts (there would be rules for who can post, who can read). This could easily include documents. We could essentially implement this as a group mailbox, with some small modifications. > -- News reader???? > > None of the above have any priority, I was just throwing out ideas > since I can't code at the moment. Most involve more client side > work, so the client people can determine priority. > > Just something to think about it. > > Shane > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ > > _______________________________________________ > Agendaware-dev-server mailing list > Age...@li... > https://lists.sourceforge.net/lists/listinfo/agendaware-dev-server > > > |
