<ok> RE: [jdev] Permanent data storage

[Bresler, Jonathan]

No, nothing additional.

-----Original Message-----
From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf Of Ivan Blecic
Sent: Friday, October 22, 2004 1:48 PM
To: jdev at jabber.org
Cc: ckadara at nerim.net
Subject: Re: <ok> RE: [jdev] Permanent data storage



Yes, I knew about that one, but I need a more general model for storing 
data in the DB. All my graphical schemas would basically be graphs, so I 
need to store data. Also,

I think the Coccinella whiteboard is not permanent. The drawing is there as 
long as there are on-line users.

Any other help?

Thank you anyway.
Cheers,
Ivan

At 19.36 22/10/2004, Bresler, Jonathan wrote:
>Please take a look at Coccinella: http://hem.fyristorg.com/matben/.
>It is a jabber client with virtual whiteboard capabilities.
>
>Jonathan Bresler
>
>-----Original Message-----
>From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf 
>Of Ivan Blecic
>Sent: Friday, October 22, 2004 11:54 AM
>To: jdev at jabber.org
>Cc: ckadara at nerim.net
>Subject: [jdev] Permanent data storage
>
>
>
>Hi all,
>
>I was looking for docs on this issue, but couldn't find anything useful, so
>here is my question.
>
>I would need something like a permanent data storage (possibly a relational
>database, let's say mysql).
>
>Here's the scenario:
>
>I would like to develop a client that, besides including the standard IM
>features, allow users to draw graphical schemes (if someone is interested,
>I could explain more on that, but for the purpose of my question it could
>be enough).
>
>So, basically, users would have something similar to a virtual whiteboard
>and would do the drawings in a collaborative way.
>
>Now the issue is that I would like to store the graphical scheme
>permanently into a database, so when one logs in, he/she is able to get the
>current drawing.
>
>Another issue is to have real-time drawing update.
>
>So, as I see it, this is theoretically what should happen when an user
>draws something (let's say a line):
>
>1. User draws on the drawing canvas of the client application
>2. The client sends to Jabber the XML description of that graphical element
>3. Jabber stores that into a database
>4. Jabber broadcasts the update to other connected clients.
>5. Other clients update their drawings.
>
>So, fundamentally, my questions is: does anyone have any suggestions on
>features, already available components, examples, experiences useful in my
>case? Will I have to develop a new Jabber-to-database component?
>
>Any hint?
>
>That you in advance.
>
>Best regards,
>Ivan
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mail.jabber.org/mailman/listinfo/jdev
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.776 / Virus Database: 523 - Release Date: 10/12/2004
>
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.776 / Virus Database: 523 - Release Date: 10/12/2004
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mail.jabber.org/mailman/listinfo/jdev
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mail.jabber.org/mailman/listinfo/jdev

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.776 / Virus Database: 523 - Release Date: 10/12/2004
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.776 / Virus Database: 523 - Release Date: 10/12/2004