Home   Info   DevZone   Wiki  
UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
JipDiscussion ] [ not logged in ] [ Web: Imported ] goto:  options
[ get info on or edit ] login or new user ] [ list of topics, hubs & nodes, or recent changes ]

Jip Discussion Page

This page is for discussing the Jip (Jamund/Iain/Peter) project. If you have any features you would like to see please put them on the JipWishList not here.

If you modify this page we request that you sign your comments.


Please add any thing, dont take anything off, but write below the item if yoy find a problem with it.

Stored Data

Viewable Data UIs Other things -- JamundFerguson (05-02-99)
* OK I just said JosProjectClient meaning whatever client is used by someone that owns a project to update data on the project list. So it should be an interface or abstract class that has general definitions, because things work differently in an app as opposed to an applet. -- JF (05-02-99)

-- JamundFerguson (05-02-99)

We need a standard way to store data, as far as I know it is all text data. What about possibly storing it in an XML format? Or maybe storing the data on the clients computers (about his/her project) in some XML format, and then storing it on the server side in a database with JDBC? Just a though, I don't really have any compelling reasons for doing this way, but I think it sounds good, and maybe if we had a proposition it could be implemented in the near future.


Well, I pretty much agree with everything said above, except that I don't think it is necessary to store the data in XML locally on the client side (unless different applications will want access that same data). Sending the data to the server in XML, on the other hand, sounds good.

As for LiveConnect, I'll hold off commenting until I know what it is :)

-- PeterSchuller


Lets store it in XML on the client side, so won't have to transform it on the way to the server.

The data stored on there will just be used by the client to remember the persons last data, so they can just change the old data, instead of re-writing it all of the time.

The reason for saving it in XML, is that it will just be simpler for us to create more than one client, or if we make a JosControlPanel as well as the JIP thing, it will be better to have a standard data format.

Also pushing XML data to a database is pretty easy, and we could create a way to do it that could be used for more than this small project.

- JamundFerguson


As for uploading, I was confusing this with a more general Jos Control Panel or something of that nature.

And what about liveconnect? I don't know one thing about it, but would prefer using a more standard approach.

I am going to get rid of some of my old comments, feel free to do the same, to clear stuff up...


Okay...


About XML again. The reason I was reluctant to use XML on the client is that, as (someone, who?) pointed out above, that would need a parser, which, even though it's no big deal if we limit ourselves to whatever functionallity is needed for this project, still requires more coding than just senind the data in XML.

I don't know the specifics on XML, but I've got the impression it's pretty good, and I don't have anything against it per se.

Just wanted to clear that up, in case I sounded somewhat unwilling to co-operate last time :)

-- PeterSchuller


This project is brought to you by JamundFerguson, IainLowe and PeterSchuller 
Page last updated 05-02-99 by IainLowe



Content of these pages are owned and copyrighted by the poster.
Hosted by: