Exceptions checking

Ruslan Zasukhin sunshine at public.kherson.ua
Sun Sep 14 13:32:15 CDT 2008


On 9/14/08 9:20 PM, "Bart Pietercil" <bart.pietercil at cognosis.be> wrote:

Hi Bart,

>> Yes, this idea is our dream
>> 
>>    VRecources/English/*.xml
>>    VRecources/German/*.xml
>> 
>> Third party developer must be able translate xml files self, put
>> them into additional folder, and setup own language.
>> 
>> I think name of language should be the same as name of folder,
>>    so in SQL will sounds like
>> 
>>        SET PROPERTY Language OF CONNECTION TO 'German'
>> 
>> And engine must search for folder with such name and load XMLs from
>> there.
>> 
>> This feature not works yet. Request via Mantis if needed.
> 
> I think it would be a mistake to name the file after a language. Years
> of experience in multi-lingual programming has let me to believe
> that the only viable soultion is specifiying the full file path (or
> directory in this case) to use at the connection level.
> 
> In our case that would be
> SET PROPERTY exceptiondirectory OF CONNECTION TO 'specify a FULL path
> here'

Hmm, I do not see need in this!

You now think about VSERVER, but the same should work for e.g. V4RB LOCAL
app. So we exactly cannot use absolute path here Bart.

V4RB app know self where is vcomponents folder, so it is able locate
VRecources folder. And inside of it find folder with name "Language".

What problems you see here ?


> we need to be able to specify a full path here because then the only
> thing  needed is that the vserver can 'reach out' to this directory.

> The reason I want it OUTSIDE of anything that has to do with Valentina
> is because I want to be able to parse the xml from the client app.
> In our case that would be PHP.
> 
> And I most certainly do NOT want to give APACHE  webacces to a
> directory that leads to the database engine (seems silly from a
> security standpoint).
> So I want it the other way around, no files inside Valentina Paths but
> being able to specify to valentina where it can find the files to use
> in exception reporting.

Aha, I see your point of view.

> It seems to me it would be a minor change for Valentina and it would
> make the xml solution immediately workable for all clients that know
> how to handle an xml-file.
> 
> Hope you get the idea

Now question is 

    1) what task is MAJOR for you and how much urgent?

    2) what way you prefer... Absolute path to what?
        folder with 2 our XML files?

    3) or you need yet THIRD XML file?

Ivan have try today add codes to our XML files, as you can do, and says this
works. Only issue with this way -- you need correct this file after each
install.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list