Hello,

I have advanced a lot in the development of the common authentication
extension for jdbc and mongo. At this moment I have a stable enough version
to share it with you and together find all possible faults that remain to
be resolved.
I am aware that there are several errors in the application, but I have a
deployment booted with MySQL and MongoDB. The two deployments are
accessible and you can navigate well through the different options, I ask
for your help to find the errors that may arise when making the different
possible cases in the application since I do not know the whole functional
part.
If you agree I prepare the pull request with my development, this includes
two new libraries, the implementation of the guacamole database with
morphia using mongodb and the shared library with all the common code
between morphia and jdbc for authentication. In addition to the adaptation
of the existing libraries of jdbc to use the new common dependency.

The name of the classes that I have used may not be suitable, since to
guide me I chose to name all the classes and interfaces, which had to be
reimplemented in the specific parts of jdbc and morphia, as an abstract in
the final part of the name . This will be refactored at the end of the
development with a more coherent nomenclature.

I hope that the development is at the level you are looking for.

I feel if the language used is not adequate, I do not speak the language
correctly.

A greeting.

El mar., 8 ene. 2019 a las 17:32, Daniel Quirant Rico (<
[email protected]>) escribió:

> Hello,
>
> Thanks for your interest.
> I have finished the integration and I am solving small errors. During the 
> next week I will try to upload the code, depending on the time I have free to 
> finish reviewing the code, and you can help prove it.
>
> PS: I've noticed that in a previous email I mentioned that I was working on 
> version 0.9.4, I meant 0.9.14.
>
> Greetings.
>
>
> El dom., 6 ene. 2019 15:26, fou fe <[email protected]> escribió:
>
>> Hi
>> I m interesting to test your extension.
>> If you need help i m here.
>>
>> Fouad
>>
>> Télécharger Outlook pour Android <https://aka.ms/ghei36>
>>
>> ------------------------------
>> *From:* Daniel Quirant Rico <[email protected]>
>> *Sent:* Thursday, January 3, 2019 2:16:17 AM
>> *To:* [email protected]
>> *Subject:* Re: Guacamole extensión MongoDB
>>
>> Hello,
>>
>> I still work hard on the common base extension, a week ago I finished the
>> development but there were many changes since I initially fork.
>> I have updated my fork and am adapting the whole new part of the user
>> groups to be able to run all the databases. By mistake when updating my
>> fork I created a pull request, I feel the confusion.
>> The adaptation completed for version 0.9.4 looks very good, I will
>> continue
>> working hard until I complete version 1.0.0.
>> If you wish, I can upload version 0.9.4 so you can take a look.
>>
>> Greetings and happy new year.
>>
>> El lun., 17 dic. 2018 a las 21:31, Daniel Quirant Rico (<
>> [email protected]>) escribió:
>>
>> > I'm going to review the code a bit more to clean it, for now I have the
>> > morphia part running, I'll check that everything works in the sql part
>> and
>> > I'll do a pull request so you can check it.
>> >
>> > El vie., 14 dic. 2018 a las 12:55, Nick Couchman (<[email protected]>)
>> > escribió:
>> >
>> >> >
>> >> > I think I have explained it more or less well, it is possible that my
>> >> > expression in the language is not the most appropriate since I do not
>> >> speak
>> >> > English well.
>> >> >
>> >> > I hope you respond with ideas and proposals, as well as your opinion
>> on
>> >> > what I am trying to solve.
>> >> > If you need to see the code, I can share it without problem, even if
>> it
>> >> is
>> >> > not completely finished.
>> >> >
>> >>
>> >> I think you did a great job of explaining it, but I do better seeing
>> >> actual
>> >> code, so if you wouldn't mind sharing examples of what you have, that
>> >> would
>> >> probably be best, at least for me.
>> >>
>> >> -Nick
>> >>
>> >
>>
>

Reply via email to