Does anyone know the URL for using the Mojo messaging service with the device. I can get it to work with the emulator from Google App Engine and .NET but it does not work on the device. I've read in some other forums that it may be related to the URL.
Anyone have any information. The URL I am currently using is https://ps15.sb.palm.com/palmcsext/services/deviceJ/publish
Per the docs http://developer.palm.com/index.php?option=com_content&view=article&id=1671 :
The Mojo Messaging service is
currently in beta and is not yet
available for production deployments.
Developers with apps nearing readiness
should contact Palm developer support
to inquire about deploying as part of
the beta program.
This means that it only works on the emulator because its running a developer version of the ROM for beta testing - against developer/beta servers. There is not currently a developer ROM available for the devices, so you can test this on the devices at the moment. The production ROM runs against different messaging servers that are not available .. yet.
Related
Apple App Store rejected my app with this message:
We discovered one or more bugs in your app when reviewed on iPad
running iOS 11.4.1 on Wi-Fi connected to an IPv6 network.
Because of this I (too late) discovered that since June 2016 Apple requires that every app submitted to App Store should support IPv6-only networking, as written here https://developer.apple.com/support/ipv6/:
Starting June 1, 2016, all apps submitted to the App Store must
support IPv6-only networking. A majority of apps will not require any
changes as IPv6 is already supported by NSURLSession and CFNetwork
APIs. However, if your app utilizes IPv4-specific APIs or hard-coded
IP addresses, you will need to make changes. Be sure to test for IPv6
compatibility before submitting your app to the App Store for review.
The point is that my app doesn't have hardcoded IP addresses and for all the web calls I simply instantiate an HttpClient with default implementation; I already submitted other app based on the same one for other clients, but it's the first time that they rejected it for this reason. Moreover I don't have a way to do a test with IPv6 because my ISP doesn't support it, and also APN of my two mobile sims (internet.wind and mobile.vodafone.it) doesn't work in IPv6.
Is it possible that Apple does this test only once in a while and with other 5/10 submissions I was simply lucky?
After I discovered that the problem was due to the server, that during night (my night, afternoon in USA) was very slow, but reading documentation I've found this, that could be useful to other people:
https://learn.microsoft.com/en-us/xamarin/cross-platform/macios/http-stack
April, 2018 – Due to increased security requirements, including PCI
compliance, major cloud providers and web servers are expected to stop
supporting TLS versions older than 1.2. Xamarin projects created in
previous versions of Visual Studio default to use older versions of
TLS.
In order to ensure your apps continue to work with these servers and
services, you should update your Xamarin projects with the
NSUrlSession setting shown below, then re-build and re-deploy your
apps to your users.
So yes, for HttpClient implementation managed is the default option, and it's almost sure that if you have an old application on the iOS project settings you'll find that one. But Xamarin now suggests to use the NSUrlSession, so to avoid problems in the future is probably good to change it.
But it's almost sure that if you don't have any hardcoded IPv6 address you don't have to change anything in your code:
https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html
If you’re writing a client-side app using high-level networking APIs
such as NSURLSession and the CFNetwork frameworks and you connect by
name, you should not need to change anything for your app to work with
IPv6 addresses. If you aren’t connecting by name, you probably should
be.
I need to install the HPE Mobile Center Connector on my local pc without any server just for a trial with UFT. can anyone advice what should i give in the Mobile center IP Address? since server port is by default: 8080
If you want to test mobile with UFT you need to have a mobile center server installed.
The Mobile Center Connector is not used by UFT, it's just a way to connect mobile devices to the MC server without physically connecting the device to the server machine. You should think of the connector as a way to extend the MC server. UFT connects to the server and can see all devices connected to the server (either physically or via connector) so if you don't have a server machine the connector has no meaning.
You can install the MC sever on a virtual machine if this helps.
You can install MC all in one which includes server + connector. It's supported for both Windows & Linux.
There is a trial version so you can test it with UFT.
If you want to try out Mobile testing with UFT, there is a free resource that you can use:
https://marketplace.microfocus.com/appdelivery/content/uft-mobile-add-in-for-local-device
More info from Micro Focus marketplace:
"This “add-in” acts as a connector between UFT and the mobile devices connected directly to the UFT machine. In just a few steps, UFT users can start designing and running mobile app and web tests on one local mobile device at a time without purchasing an additional license. Whether you work in Retail, Telecom, Finance, or other adjacent industries, the UFT Mobile Add-in for Local Devices is a great fit for testers who need to:
Execute their omnichannel content strategy using the same script for desktop and mobile web content
Support mobile testing in organisations that do not have a lab management solution in place
Run mobile tests without needing a new tool for mobile only"
I recently installed Windows Server Service Bus 1.0 (on a Windows Server 2008 R2 machine).
That also installs "Windows Fabric" (not AppFabric).
Could not find much information on it, and googleing it I stumbled on a Lync server post (Windows Fabric is also installed by Lync Server 2013).
Definition:
"Windows Fabric is a Microsoft technology used for creating highly reliable, distributable, and scalable applications."
From the Service Bus architecture intro,it looks like Fabric is what allows for services replication, high availabilty, and fault tolerance.
Anyone knows if that can be used to host custom .NET services? Or any kind of direction would be greatly appreciated.
Thanks in advance.
Cos
I went to a talk by Mark Eisenberg on May 28th at the Microsoft NERD Center near MIT in Boston MA. The talk was mostly about the Azure Service Fabric. General consensus was that if you're using Azure from the infrastructure as a service perspective you aren't really using it.
The next step up is to use Azure naively as a platform meaning that rather than create VMs and hosting them there you're creating cloud services and web jobs and web apps and using the new Logic Api's etc...
But if you really want to build a stateful, resilient service enterprise class you'll want to go underneath the PaaS and write against the Service Fabric directly for greater control.
That's where the money is.
I did a write up on the talk and what the Azure Service Fabric is a few days ago and posted it here.
I don't actually think that Windows Fabric is open product. It is used for infrastructure purposes, and not for deploying custom services. For your custom services you have to use platform built on top of Windows Fabric, like Service Bus, Windows Server App Fabric.
I think Windows Fabric is for internal use by Windows Azure and Private Cloud for clustering, load balancing and so on.
UPDATE:
I've started developing Windows Azure application and here is what I've found.
I've added a Service role to Azure application and started it on local development machine (under Azure emulator). And my service was published in and started under Windows Fabric!
So the conclusion is: Windows Fabric is a platform for running YOUR Cloud Services.
Fabric which the name suggests in itself, is back-end.
It is no different than iSCSI or EIGRP. The main difference is that it is generic in form rather than specific like the aforementioned services/protocols.
IIS is a server service specific to web hosting.
SQL the same but database only..
fabric, applied to host fabric aware services and software.
Windows Fabric is used internal by Microsoft to building highly available, resilient and scalable services. It has been used for Service Bus, SQL Database, Document DB etc. according to this video: Building Resilient, Scalable Services with Microsoft Azure Service Fabric
Until now it has not been available for external parties but has now been announced as Service Fabric which will be available on Windows Azure and Window Server 2016.
Read more here: http://azure.microsoft.com/en-us/campaigns/service-fabric/
This question has probably less to do with actual programming and more to do with environment setup.
I'm developing an application for a Windows CE device, which will use a service hosted in Microsoft Azure. Obviously, this is all under development, and the service itself has not yet been uploaded to Azure. So I'm using the emulators provided by MS to deploy the service locally. Also, I don't think uploading the service to Azure just to debug it is a good idea, as that could net us a bill for Azure we don't yet want to pay.
Also, please note, I'm using VS2008 for the Windows CE project and VS2010 for the Azure project (thank you MS for dropping support for mobile devices -_-).
The problem is, the service seems to be accessible only via 127.0.0.1 or localhost, and if I physically connect a Windows CE device or use an emulated one, it becomes a new entity on the network, and cannot access that service any more.
How can I debug my Window CE application and have it see the service, whilst still being able to debug the service itself?
You are correct, the development fabric (the compute emulator that allows you to build an azure application and debug it locally) is only meant for local development. There are some hacks that allow you to get around that, but I wouldn't recommend it.
My recommendation would be to spin up the service in a more traditional hosting environment, at least in these early stages. You can define it as a web app just as you always would have, and get it functioning. Then, when you know its mostly complete, create a cloud service project and do an add existing to bring your web app into the cloud service solution. Once in, its a simple matter to add the web app as a web role.
From there, you can complete testing of the service in both the local and hosted azure environments as needed. This allows you to minimize your development costs while still leveraging the power of the cloud. As an upside, you also have done most of the basic work to ensure your service is compatible with multiple deployment scenarios giving you a greater degree of choice for its final production state.
OK, I don't know if this was intentional, or if I found one of the mentioned hacks, but I saw that IIS hosts the Azure site I created on port 5100, and the binding for this site is *, so it accepts all connections.
Using this I could access the service from my emulator, and I could still debug all Azure related stuff.
I'm trying to find a way of automatically discovering and communicating with a local network service running on desktop/laptop. Much like the Zune's wifi sync feature.
iPhone can do this using Bonjour service. Is there anything like that on WP7 platform? Any other suggestions?
There is currently nothing like this available in the SDK.
Network operations are currently very limited and you're restricted to HTTP based connections. I'm not sure how useful that would be for the scenario you describe.