[x3d-public] Fwd: Multiuser: Centralized scenegraph repository with Git

[John Carlson]

Is git fast enough?

John

On Wed, Feb 24, 2021 at 11:10 AM Christoph Valentin <
christoph.valentin at gmx.at> wrote:

> Hi John,
>
> Sounds good and interesting. If nobody else supports this, then I'll
> probably look for a solution.
>
> Give me a day (by tomorrow I must finish my technical input for a bid),
> then I'll take two days off (Fr - Mo).
>
> Will think about a solution, probably based on "the society"'s vServer/VPN
> and/or the GitHub repository github.com/christoph-v/spark.
>
> KR
> *Gesendet:* Mittwoch, 24. Februar 2021 um 17:15 Uhr
> *Von:* "John Carlson" <yottzumm at gmail.com>
> *An:* "Christoph Valentin" <christoph.valentin at gmx.at>, "X3D Graphics
> public mailing list" <x3d-public at web3d.org>
> *Betreff:* Re: Aw: [x3d-public] Fwd: Multiuser: Centralized scenegraph
> repository with Git
> Another thing I should be able to do is generate statistics of the
> scenegraphs with standard Linux tools.
>
> John
>
> On Wed, Feb 24, 2021 at 3:12 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> I'm not sure why, and possibly, it's throwaway code.
>>
>> 1) provide a way to synchronize a scenegraph between client/server
>>
>> 2) provide a way to synchronize a scenegraph between multiple peers
>>
>> 3) Try out the UNIX "everything's a file"  philosophy.
>>
>> 4) Experiment with data structure on top of a file system, persistent
>> data structures that don't go away after the process exits.
>>
>> 5) Experiment with configuration management of scenegraphs.
>>
>> Umm
>>
>> Has anyone hooked Git into a browser?
>>
>> John
>> On 2/23/21 11:57 PM, Christoph Valentin wrote:
>>
>> Good Morning, John.
>>
>> I think I've understood now, HOW you want to do it.
>>
>> Just I cannot catch the WHY.
>>
>> Indeed, it would be a new encoding type.
>>
>> Why not just upload the files to git, as they are? Is it because you have
>> more freedom, when putting the scene together from nodes and routes?
>>
>> In this case I would not only provide a directory in a github repository,
>> but also TWO ACCOUNTS AT THE OWNCLOUD FRAMEWORK,
>>
>> one for authoring/composing the scene, the other for playing the game.
>>
>> looking fwd to your answer
>> Christoph
>>
>> --
>> Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail
>> gesendet.
>> Am 23.02.21, 23:21 schrieb John Carlson <yottzumm at gmail.com>
>> <yottzumm at gmail.com>:
>>>
>>> I can lay it out here in a description where you take X3D JSON objects
>>> and convert them to folders and files.
>>>
>>> JSON objects are converted to folders.
>>> Keys become folder names and file names.  MFNode JSON arrays are
>>> converted to a whole number indexed filenames. Values are stored in files.
>>>   Ordinary MF fields (eg. MFInt32) are stored inside files.
>>>
>>> One will also need to do round trip.
>>>
>>> Updates/pulls/pushes are done through got.
>>>
>>> John
>>> ---------- Forwarded message ---------
>>> From: Christoph Valentin <christoph.valentin at gmx.at>
>>> Date: Tue, Feb 23, 2021 at 11:24 AM
>>> Subject: Re: [x3d-public] Multiuser: Centralized scenegraph repository
>>> with Git
>>> To: X3D Graphics public mailing list <x3d-public at web3d.org>
>>>
>>> Hi John,
>>>
>>> I've been using gitlab and github at my employer's.
>>>
>>> Coincidally I've got three github repositories, where at least one would
>>> fit to the topic.
>>>
>>> I was considering to use file sharing with the owncloud framework.
>>>
>>> What exactly do you need? What will be the topic of the prototype?
>>>
>>> You can send a PM at facebook, if you want to keep the details private.
>>>
>>> kr
>>> Christoph
>>>
>>> --
>>> Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail
>>> gesendet.
>>> Am 23.02.21, 17:38 schrieb John Carlson <yottzumm at gmail.com>:
>>>
>>>> It not what you think. I propose the real-time and multi-user database
>>>> solution based on git.
>>>>
>>>> This would provide a 3rd X3D encoding, encoded in an online file system,
>>>> similar to WebDAV or Git.
>>>>
>>>> Updates are done through push and pull requests.
>>>>
>>>> Security and extra features would be provided by git (gitlab, bitbucket,
>>>> github, etc.)
>>>>
>>>> This would make a good first prototype.   Then we could proceed with
>>>> optimization.
>>>>
>>>> So, how does one store the X3D nodes and statements in a file system?
>>>> Anyone?
>>>>
>>>> Has anyone dealt with git source code?
>>>>
>>>> John
>>>>
>>>>
>>>
>>> _______________________________________________
>>>> x3d-public mailing list
>>>> x3d-public at web3d.org
>>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>> _______________________________________________
>>> x3d-public mailing list
>>> x3d-public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>> _______________________________________________ x3d-public mailing list
>>> x3d-public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210224/cb0cbd6b/attachment-0001.html>