Daniel John Debrunner (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12423202 ]
Daniel John Debrunner commented on DERBY-464:
-
I would say one definition of sub-task is that the main task is not
Kristian Waagan wrote:
Daniel John Debrunner (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12423202
] Daniel John Debrunner commented on DERBY-464:
-
I would say one definition of sub-task
Yip Ng (JIRA) wrote:
My name is Yip Ng and I would like to contribute to the Apache Derby
project.
Welcome to the project Yip. I just tried to make the information for new
devevlopers easier to navigate on the wiki, at
http://wiki.apache.org/db-derby/DerbyDev
I'd appreciate any
Thanks Dan for the informative links. I'll definitely
take a look at them to start my Derby journey. =)
I opened DERBY-1538 to track the issue I have found
but
since I don't have developer access to JIRA, I can't
link it to DERBY-464...
--- Daniel John Debrunner [EMAIL PROTECTED] wrote:
Yip
Satheesh Bandaram (JIRA) wrote:
All implement check() interface that is used to invoke permission checking
for that access descriptor. Access descriptors already know what they need to
check for and are passed current user authorizationId.
Since g/r is a language issue, it seems like the
OK... I will see if check() method interface can be changed..
Satheesh
Daniel John Debrunner wrote:
Satheesh Bandaram (JIRA) wrote:
All implement check() interface that is used to invoke permission checking for that access descriptor. Access descriptors already know what they
Hi Francois,
I will update functional specification with system table schema. I will
also add a high level design section there with some details. I am
little pressed for time right now, but will get this out next week.
(happens to be my off week, but open source world never sleeps, right?)
Thanks Satheesh - much appreciated ;)On 12/16/05, Satheesh Bandaram [EMAIL PROTECTED] wrote:
Hi Francois,
I will update functional specification with system table schema. I will
also add a high level design section there with some details. I am
little pressed for time right now, but
Hi Satheesh,
I'm reviewing the part I changes you checked-in - there is a lot of
changes and it is somewhat tedious to understand some of the decisions
that have been made at the implementation level - not saying anything
is wrong - it is just hard to follow certain paths without a minimum of
Hi, Satheesh. I am still learning the Apache Way, so I wanted to get
some clarity on how things are generally done.
I know that committers have the merit and trust to commit what they
want. I had generally assumed, however, that a large change like this
should be posted as a patch for
Hi David,
I did post the patch for review... I followed up the post after few days
to invite anyone to review again. That time I said I could wait for
review comments or submit then address comments. I also said I would
submit the patch over the next weekend. Since no one replied that either
they
Thanks, Sateesh. Sorry, I missed the request for review comments. No
need; I personally am not able at this time to review your changes. I
just thought this was the first time we saw these changes. My mistake.
David
Satheesh Bandaram wrote:
Hi David,
I did post the patch for review... I
Why exactly would we want to strengthen builtin-authentication scheme
when all of us agreed it was for simple embedded application use? I am
not sure how useful access control is for embedded usages.
But I will hold off on any more questions and wait for your proposal.
Satheesh
Francois
Derby's Built-in authentication can be used in a client-server mode
today along with DRDA's secure transport mechanisms of users'
credential across the wire. Originally, we had no cloudscape network
driver besides 3rd party ones which were NOT providing secure transport
of user credentials across
Francois Orsini (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12356032
]
Francois Orsini commented on DERBY-464:
---
The way I implememted users in Cloudscape originally was done in a
Cloudscape running
Francois Orsini (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12356032
]
Francois Orsini commented on DERBY-464:
---
The way I implememted users in Cloudscape originally was done in a
Cloudscape running
Agreed since we always made it clear that users could be defined at the system and/or database level ;)
However, even as of today, databases can be dependent on users defined
at the system level if you have 'derby.database.propertiesOnly' set to
false which is the default I believe ;)
What I
17 matches
Mail list logo
