Is there simple documentation of the latest ITfoxtec Identity NuGet's, at least initialization and the API's, that can be used instead of solely looking at the example projects and trying to extract them?
You can find some dokumentation her https://www.itfoxtec.com/identitysaml2
Related
I have problem with etcd v2. I am creating configuration management which is using etcd v2 as K/V store. Now I do need version history as well but looks like v2 does not support it at least not straight out from the box.
I have been reading their API and at least v3 do have version/revision in response. Is there any way I could get version into v2 response as well?
Only solution currently I find is to use custom suffix with version numbers. Also using running number (POST instead of PUT) but looks like it is more as ID than version (every new or modified will increase that number)
Any ideas? Custom database to store previous versions only proper solution?
Found out that v2 does not support versions (feature in v3). I created own logic to handle versions.
I have been bit by a bug in the JSON parser in Gatling 1.5.5 which I read is solved by migrating to 2.0.
The challenge is, there is very little documentation (that I have been able to find) on Gatling 2, aside from: https://github.com/excilys/gatling/wiki/Gatling%202.
What state is the complete 2.0 documentation in, and is it accessible online yet? If so, can I get a link?
Upcoming Gatling 2 documentation (targeting current snapshot) is now stored in the repository, along with the sources.
I'm an avid GAE/J user, now trying to create my first GAE/go project.
What are the limitations of the AppEngine Go runtime compared to Java or Python runtimes? Missing APIs? Runtime limitations?
https://developers.google.com/appengine/features/ covers what features are implemented by which runtimes.
What I was able to find out so far is:
DB Query: missing composite filters (AND and OR).
DB Query: missing "member of" filter operator (IN).
No App Identity API Edit: this seems to exist, but is not listed under services
No Prospective Search
I think the title is self-explanatory.
I don't see anything on the Apache Solr wiki that suggests you can maintain the schema of an Apache Solr instance using the ReST API, but maybe (hopefully) you know something I don't.
I just found a section on the Solr wiki where they describe this exact feature for release 4.4 (which is not released yet).
It does have some prerequisite configuration on the Solr instance, but it does allow you to add fields to the schema. Based on that information, I can't see why they won't eventually extend the functionality to allow you to delete as well. I guess we will have to wait and see.
Here is the link to that section: http://wiki.apache.org/solr/SchemaRESTAPI#Adding_fields_to_a_schema. It also references this JIRA issue: "In preparation for dynamic schema modification via REST API, add a "managed" schema facility".
I'm using Go for Google App Engine, which uses an older version of Go. I want to use a third party package that requires a newer version of Go (goauth). It is possible to use that package in my Google App Engine program?
Goauth uses strings.SplitN, which does not seem to be present in the GAE version of Go.
Not without hacking the source of oauth to make it compatible, I'm afraid.
Either that, or you can try and contact the author to see if they are willing to publish a version compatible with AppEngine's Go version.
A third option would be to find an older revision of oauth which is compatible with your Go version and just use that one.