We are calling the REST version of CreatePassengerNameRecordRQ in Sabre's test environment with no issues. However, there does not seem to be a REST version of GetReservation.
Is this true? Why would only some of the APIs be available in REST?
There is an early version of a new getBooking API that Sabre is in the process of development. Based on what attributes/elements of the Reservation you are need this could meet your needs.
https://developer.sabre.com/docs/rest_apis/trip/orders/booking_management
Related
I am trying to create discord bot with all new features. Today I saw this and i can't find out how to do that.
These are Message Commands. This feature will be released in discord.py 2.0
discord.py 2.0 is the next major version of discord.py is currently in development. You can track the development here
message commands in the discord API docs
Alternatives
VoxelBotUtils (pypi) VoxelBotUtils (VBU) is an extension for Discord.py to speed up Discord bot development. It includes a whole slew of features that are commonly used in a lot of bots so you don't need to keep writing them every time.
I don't think that this is in the current version of discord.py. However, there is beta versions of discord.py that maybe has these features, you'll have to join the discord server and get the beta tester role (which is public). the link is here:
https://discord.gg/dpy
Both have their own documentation and I see only small wording differences between those. Are there list of things that have actually changed? Has OCR for example improved on version 2.0 or it's the same except I guess the handwriting recognition? Some kind of changelog would really make a difference.
The only difference between v1.0 and v2.0 is the revised /recognizedText which has a breaking change in the input/output. All other endpoints are exactly the same. Also, if you have an key in an up-to-date pricing tier (including free), your API key will work in both versions.
As you may know, the Computer Vision API has two different OCR endpoints. The /ocr endpoint runs the older recognition engine with broader language coverage. The newer /recognizeText endpoint, which in v1.0 handled handwritten text, in v2.0 covers both handwritten and printed text using a newer engine. The /recognizeText endpoint remains English-only for now. You select between handwritten/printed modalities using the mode query parameter. See
documentation here.
As for documenting changes, there isn't one obvious place for this unfortunately. One option is to check the swagger repo.
I have in fact couple question regarding that library, hopefully anyone to answer avoiding create separated topics. If that's not the place to ask let me know where please. Nevertheless i think your answer find other people to get knowledge as well because saw lot of confusions on internet regarding that staff.
Q's:
I see that current SignalR version is 2.2.3 however i cannot find any relase notes for that - only for 2.2.2, does somebody knows why?
Is there any risk updating from 2.2.1 to 2.2.3? I have such big appliation in my current version would all work as it was or is there
anything that has to be changed migrating to most recent version?
Is there any diffrence with SignalR, SignalR2 and SignalR ASP.NET? I am bit confused
Is SignalR also permitted to be developed in commercial use or do i need any specific license?
I've found lot of samples based on signalR howeever could you provide most up to date sample showing all recent feature from current
release.
Last question: Is there any significant change comparing version 2.2.1 and 2.2.3 especially related to async usage or it's more like almost the same creating server/client apps?
On this page i see nice tutorial how to use signalr, however is this page official always updating to the current signalr release?https://www.asp.net/signalr . Aksing because saw also github page any others. If not could you direct me to correct one please.
Is this sample up to date regarding new features?
There was chat saple available JabR if recall, is there still a working link to this sample?
As far as i was able to create some chat i wonder how JabR stores chat conversations history in the way that every client whom joined chat could see conversation which was done when he was not connected. In other words how to make every new joiner to chat to see all conversations already in chat by other users is this possible in signalR engine itself?
Many thanks to whoever answer.
I'm trying to answer your questions.
Already mentioned, only a single fix.
It worked for my application, can't really tell if it works for yours. More infos regarding the 2.2.2 release: https://github.com/SignalR/SignalR/releases/tag/2.2.2
I'm not quite sure what you mean. But yes there were different versions of SignalR other the last years:
SignalR 1 (2012-2014)
SignalR 2 (2014-now | Current version: 2.2.3 | Github: https://github.com/SignalR/SignalR)
SignalR '3' (aka ASP.NET Core SignalR | Release: mid 2018 | Current pre version: 1.0.0-rc1-final | Github: https://github.com/aspnet/SignalR)
I guess, not that I'm aware of. See https://www.microsoft.com/web/webpi/eula/net_library_eula_ENU.htm (SignalR 2)
https://raw.githubusercontent.com/aspnet/Home/2.0.0/LICENSE.txt (SignalR 3)
Checkout the samples here: https://www.asp.net/signalr They all target SignalR 2 currently and will be updated as soon as ASP.NET Core 2.1 and SignalR '3' is released.
Don't know, I haven't changed anything in my code.
As already mentioned in 5., they will update the page as soon as ASP.NET Core 2.1 is released (see comment section in https://blogs.msdn.microsoft.com/webdev/2018/05/07/asp-net-core-2-1-0-rc1-now-available/ )
I guess?
Do you mean this one: https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/tutorial-getting-started-with-signalr ?
I'm not aware of a SignalR feature which stores messages. I think you have to implement this yourself.
Just wanting to see if others are experiencing issues with the Google Maps API.
I am using an unversioned call to load the google maps api :
<script async defer src="https://maps.googleapis.com/maps/api/js?callback=googleMapsLoaded&libraries=drawing,geometry,visualization,places&key=xxxxxxxxxxxxxxxxxxxxxx"></script>
Which should pull in the latest stable api release (3.31).
As of today, it seems to be pulling in the broken experimental version (3.32)
Anyone else having this issue?
I have patched our production apps with the v=3.31 addition to the api call for the time being.
Any feedback from others appreciated.
According to the documentation, you get the experimental version if you don't specify a version (unless you are on a premium (paid) plan):
If you do not explicitly specify a version, you will receive the experimental version by default if you are on the standard plan (this includes customers who do not provide a key). If you're on the premium plan and don't specify a version, you will receive the release version by default.
I am trying to implement code where I can send and receive the SOAP messages to IBM MQ. As of my knowledge jar file are required for my code to work, but could not find any place where either I can download the files or can do whole setup of WebSphere 6.0
Do anyone have any idea how can I get it ?
Please be aware that grabbing the jar files from an MQ Server or other installation is not supported by IBM and never has been. However, because it is one of the most commonly used methods to install the MQ client for Java or JMS and fairly common in Java developer culture, IBM has provided a Java-only install option. Please see the Redistributable Clients page in the Knowledge Center for details.
As the name suggests, this install provides an MQ Client package that can be redistributed with independently developed MQ applications. While that is helpful, the main reason IBM provides it is to provide a lightweight install package that...
Contains the correct and complete set of jar files as packaged by IBM.
Is intact and verifiable against a known specification and inventory.
Can reliably be expected to perform as per the documentation set for that version.
Contains all of IBM's diagnostic utilities both in the compiled binaries and in the Java classes.
Contains additional utilities such as GSKit for managing certificates.
Can be patched using IBM's standard Fix Pack install media so that integrity of the installed classes and libraries is preserved.
When using IBM's install media and procedure, the result is far more stable but int he event something goes wrong, the presence of the diagnostic utilities and conformance to a standard install procedure can dramatically reduce outage durations.
Also, there are occasional instances in which a customer with full support entitlements is told that their non-standard installation is not supported and they need to correct it before continuing the PMR. Though this doesn't happen often, in most cases the problem is resolved when the MQ client is installed according to spec. When that doesn't fix it, at least diagnostics can proceed at a faster pace.
The link above has all the details, including links to the client downloads, and is highly recommended reading. You can also go directly to Fix Central for the downloads. Fix Central offers all supported MQ client versions and the relocatable clients come in v8.0 and up. In the download list, look for the "All Java" package.
As Tim noted, mixing client and server versions is supported, provided both client and server are currently in service. Generally you want to develop against the latest version of MQ client because it has the most recent client-side features and will have the longest service life before a version upgrade is required.
Assuming you're on a Unix platform for your queue manager, the client will be found at:
/opt/mqm/java/lib
However, all MQ clients are compatible with all queue manager versions. I strongly recommend you use a client which is still supported, which means 7.1, 7.5, 8.0, or 9.0 at time of writing. These are freely downloadable from the SupportPac website.
The SupportPacs of interest are those starting 'MQC'. SupportPac MQC8 for example contains the MQ V8.0 client.
Thanks everyone. Just an update to the above answer. In my case I have asked the WebSphere administrator for providing me the lib folders which contains all the required MQ jar files.
I have asked him to provide following files from the C:\Program Files (x86)\IBM\WebSphere MQ\Java\lib\ folders:
* com.ibm.mq.jar
* connector.jar
* com.ibm.mq.jmqi.jar
* com.ibm.mq.headers.jar
* com.ibm.mq.commonservices.jar