Clock - ROS Wiki摘要: 一、IPC通信设定 1、AndroidManifest.xml文件 一个App可以占用多个进程 // 独立一个进程取名remote(远程) Android每个进程都有一个VM 二、IBinder接口 1、使用Java Interface定义的接口，用于跨进程调用 ...
22:45 轻云沉峰 阅读(81) 评论(0)
摘要: Android进程一 1、复习结构 Engine基类 -abstract operation() 接口Interface Tire子类 -operation() 2、Process class、module、app在内存的某一区域执行，每块区域之间有一个隔阂，原则不...
22:53 轻云沉峰 阅读(95) 评论(0)
摘要: 1 imageView.setOnTouchListener(); 2 3 private final class TouchListener implements OnTouchListener{ 4 private int mode = 0; 5 private static final int DRAG = 1;// 拖拉 6 private static final int ZOOM = 2;// 缩放 7 // 存放开始点 8 private PointF startPoint = new PointF(); 9 // 矩阵对象移动...
13:10 轻云沉峰 阅读(93) 评论(0)
摘要: Android提供了两种动画 一、Tween动画也就相当于补间动画透明度变化alpha1 AlphaAnimation aa = new AlphaAnimation(0.0f,1.0f);//不透明到完全透明2 aa.setDuration(2000);// 持续时间3 imageView.startAnimation(aa);// 作用到对象上旋转动画rotate1 RotateAnimation ra = new RotateAnimation(0,90);//从0-90度2 // 旋转中心的设置3 RotateAnimation ra = new RotateAnimation(0,9
09:40 轻云沉峰 阅读(1210) 评论(0)
摘要: 一、AndroidManifest文件中1 2 3 4 5 二、新建class继承AndroidTestCasepublic void test()throws Exception{}三、右击运行Run As - Android Junit Test
16:20 轻云沉峰 阅读(56) 评论(0)
摘要: 1 电话拨号 2 Intent intent = new Intent(); 3 intent.setAction(Intent.ACTION_CALL);// 动作类型 拨打电话操作 4 intent.setData(Uri.parse(&tel:&+number));// 数据 Android中通过Uri来描述 5 startActivity(intent); 6 需要的权限 7 8 9 发短信10 SmsManager sm = SmsManager.getDefault();// 短信管理11 // sendIntent,deliveryIntent延期的意图 发送
15:56 轻云沉峰 阅读(132) 评论(0)
摘要: 因Activity关闭，而通过WindowManager添加的控件未关闭，导致无法附着报类似has leaked window android.widget的错误，只需做如下处理@Overrideprotected void onDestroy() { super.onDestroy(); mWindowManager.removeView(mDialogText);}
10:21 轻云沉峰 阅读(5550) 评论(0)
摘要: adb全称android debug bridge即android调试桥的意思拷贝文件到手机 adb push 原文件 目标文件拷贝文件到电脑 adb pull 原文件目标文件关闭adb服务 adb kill-server启动adb服务 adb start-server安装apk adb install v.apk卸载apk[包名] adb uninstall com.android.v版本号 adb version模拟器或真机控制台 adb shell横竖屏切换 ctrl + F11
15:18 轻云沉峰 阅读(42) 评论(0)
摘要: 安装新的ADT或升级时，导入之前的项目正常，但编译运行时会NoClassDefFoundError，找不到第三方jar包。解决办法：Properties-&Java Build Path-&Order and Export全部勾上即可
13:47 轻云沉峰 阅读(44) 评论(0)
摘要: 一、JDK配置JAVA_HOME D:\Java\jdk1.6.0_45配置classpath .;%JAVA_HOME%/lib/rt.%JAVA_HOME%/lib/tools.jar配置Path %JAVA_HOME%/二、SDK配置与JDK类似在Path前继续追加：%ANDROID_SDK_HOME%\platform-%ANDROID_SDK_HOME%\
18:26 轻云沉峰 阅读(74) 评论(1)
摘要: Eclipse中ADT可能出错，那么卸载重装可能比较省事，具体步骤直接如图：下一步就是选择需要卸载的因插件文件路径变更，而报错问题Some sites could not be found. See the error log for more detail，解决方法如下图：
09:35 轻云沉峰 阅读(3030) 评论(0)
摘要: 1、“回车”变为“下一步”1 android:imeOptions=&actionNext&2、“回车”变为“完成”1 ndroid:imeOptions=&actionDone&3、只显示一行1 android:singleLine=&true&4、键盘类型1 android:inputType=&number& 数字 2 android:inputType=&textPhonetic& 拼音输入 3 android:inputType=&date& 日期键盘
10:46 轻云沉峰 阅读(58) 评论(0)
摘要: 1.ServerSocket基础 用于监听特定的端口，接收Socket请求 ServerSocket server = new ServerSocket(8080); 管理客户端连接请求是由操作系统控制的，这些连接会存入先进先出的队列中，当然队列有最大限度 backlog参数 ServerSocket构造方法的backlog参数用来设置连接请求队列的长度，但不能超过系统限定的长度一个示例：View Code 1 &span&// 服务端 2 public static void main(String[] args) throws Exception{ 3 // 创建ServerS
08:16 轻云沉峰 阅读(108) 评论(0)
摘要: 1.OSI模型 物理层 传输用的物理介质，以bit(0或1)流传输，Hub就在此层 数据链路层 节点间传输，检测传输中的差错，以帧(二进制数据组成)为单位，Switch在该层 网络层 IP协议在该层，选择不同的网络,以数据包(由帧组成)为单位，路由Router在该层 传输层 传输数据，单位为报文，TCP、UDP协议就在传输层 会话层 管理进程之间的会话过程 表示层 数据的加密解密压缩与解压缩等 应用层 http、FTP、telnet等协议在该层2.TCP/IP模型 应用层 ftp、telent、http，与OSI类似 传输层 tcp、udp 网络层 IP 主机-物理层 以太网3.URL 统一资
13:37 轻云沉峰 阅读(157) 评论(0)
摘要: 一、新建继承Service的类 1 @Override 2 public IBinder onBind(Intent intent){ 3 4 } 5 //并重写以下方法 6 //第一次创建的时候调用 7 @Override 8 public void onCreate(){ 9 super.onCreate();10 setForeground(true);//服务所在进程设置为前台进程11 }12 @Override13 public void onStart(Intent intent,int startId){14 super....
12:11 轻云沉峰 阅读(36) 评论(0)MyEclipse中导入tomcat出现错误89：An error has occurred. See error log for more details（如图）. 89_百度知道
MyEclipse中导入tomcat出现错误89：An error has occurred. See error log for more details（如图）. 89
我有更好的答案
把你弄的路径截图放出来看看
这个路径？之前安装在D盘，后来重装就没改路径，是默认C盘的
不是，是你的tomcat，你添加tomcat时路径有没有弄错？把你添加的那个路径截图一下看看。
tomcat我单独启动是运行正常的，然后配置的时候是点击tomcat就会跳出错误，所以根本走不到添加路径这一步
这个你看一下
采纳率：46%
查查是不是重装之后jdk路径错了
我帮你 加 1-3
为您推荐：
其他类似问题
您可能关注的内容
deta的相关知识
换一换
回答问题，赢新手礼包
个人、企业类
违法有害信息,请在下方选择后提交
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。From Wikipedia, the free encyclopedia
Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a
to be requested from another
outside the domain from which the first resource was served. A web page may freely embed cross-origin images, , scripts, , and videos. Certain "cross-domain" requests, notably
requests, are forbidden by default by the .
CORS defines a way in which a browser and server can interact to determine whether or not it is safe to allow the cross-origin request. It allows for more freedom and functionality than purely same-origin requests, but is more secure than simply allowing all cross-origin requests. The specification for CORS was originally published as a
Recommendation but that document is obsolete. The current actively-maintained specification that defines CORS is the Fetch Living Standard.
The CORS standard describes new HTTP headers which provide browsers and servers a way to request remote URLs only when they have permission. Although some validation and authorization can be performed by the server, it is generally the browser's responsibility to support these headers and honor the restrictions they impose.
For Ajax and
that can modify data (usually HTTP methods other than GET, or for POST usage with certain MIME types), the specification mandates that browsers "preflight" the request, soliciting supported methods from the server with an HTTP OPTIONS request method, and then, upon "approval" from the server, sending the actual request with the actual HTTP request method. Servers can also notify clients whether "credentials" (including Cookies and HTTP Authentication data) should be sent with requests.
This is generally not appropriate when using the . When a CORS-compatible browser attempts to make a cross-origin request:
The browser sends the OPTIONS request with an Origin . The value of this header is the domain that served the parent page. When a page from http://www.example.com attempts to access a user's data in service.example.com, the following request header would be sent to service.example.com:
Origin: http://www.example.com
The server at service.example.com may respond with:
An Access-Control-Allow-Origin (ACAO) header in its response indicating which origin sites are allowed. For example:
Access-Control-Allow-Origin: http://www.example.com
An error page if the server does not allow the cross-origin request
An Access-Control-Allow-Origin (ACAO) header with a wildcard that allows all domains:
Access-Control-Allow-Origin: *
A wildcard same-origin policy is appropriate when a page or API response is considered completely public content and it is intended to be accessible to everyone, including any code on any site. For example, a freely-available
on a public hosting service like .
A wildcard same-origin policy is also widely and appropriately used in the , where pages have unguessable URLs and are meant to be accessible to anyone who knows the secret.
The value of "*" is special in that it does not allow requests to supply credentials, meaning it does not allow HTTP authentication, client-side SSL certificates, or cookies to be sent in the cross-domain request.
Note that in the CORS architecture, the ACAO header is being set by the external web service (service.example.com), not the original web application server (www.example.com). CORS allows the external web service to authorise the web application to use its services and does not control external services accessed by the web application. For the latter,
should be used (connect-src directive).
When performing certain types of cross-domain Ajax requests, modern browsers that support CORS will insert an extra "preflight" request to determine whether they have permission to perform the action.
Host: service.example.com
Origin: http://www.example.com
If service.example.com is willing to accept the action, it may respond with the following headers:
Access-Control-Allow-Origin: http://www.example.com
Access-Control-Allow-Methods: PUT, DELETE
The HTTP headers that relate to CORS are
Access-Control-Request-Method
Access-Control-Request-Headers
Access-Control-Allow-Origin
Access-Control-Allow-Credentials
Access-Control-Expose-Headers
Access-Control-Max-Age
Access-Control-Allow-Methods
Access-Control-Allow-Headers
CORS is supported by all browsers based on the following layout engines:
- and -based browsers ( 28+,
15+, , 's 4.4+ WebView and
WebEngine)
1.9.1 (Firefox 3.5, SeaMonkey 2.0) and above.
6.0 (Internet Explorer 10) has native support. MSHTML/Trident 4.0 & 5.0 (Internet Explorer 8 & 9) provide partial support via the XDomainRequest object.
-based browsers (Opera) implement CORS as of
12, but not .
(Initial revision uncertain, Safari 4 and above, Google Chrome 3 and above, possibly earlier).
All versions.
Cross-origin support was originally proposed by Matt Oshry, Brad Porter, and Michael Bodell of
in March 2004 for inclusion in
2.1 to allow safe cross-origin data requests by VoiceXML browsers. The mechanism was deemed general in nature and not specific to VoiceXML and was subsequently separated into an implementation NOTE. The WebApps Working Group of the W3C with participation from the major browser vendors began to formalize the NOTE into a
on track toward formal
In May 2006 the first W3C Working Draft was submitted. In March 2009 the draft was renamed to "Cross-Origin Resource Sharing" and in January 2014 it was accepted as a W3C Recommendation.
CORS can be used as a modern alternative to the
pattern. While JSONP supports only the GET request method, CORS also supports other types of HTTP requests. Using CORS enables a web programmer to use regular , which supports better error handling than JSONP. On the other hand, JSONP works on legacy browsers which predate CORS support. CORS is supported by most modern web browsers. Also, while JSONP can cause
issues when the external site is compromised, CORS allows websites to manually parse responses to ensure security.
on July 6, 2009 by Arun Ranganathan (). . Hacks.mozilla.org.
. NCZOnline.
. MOZILLA.
. W3.org. Retrieved on .
. QuirksBlog. April .
. Ars Technica. April .
. Developer.mozilla.org.
. Developer.mozilla.org. .
Tony R Program M Internet Explorer (). . MSDN.
David Honneffer, Documentation Specialist (). . Opera.
David Honneffer, Documentation Specialist (). . Opera.com.
. Osvdb.org.
. W3.org. .
. W3.org 2015.
. W3.org 2015.
. W3.org 2015.
. caniuse.com.
(the current specification for CORS)
, including:
How to avoid the CORS preflight
How to fix “Access-Control-Allow-Origin header must not be the wildcard” problems
How to use a CORS proxy to get around “No Access-Control-Allow-Origin header is present on the requested resource” problems更新ADT出现了错误，不懂？求帮忙。。
[问题点数：40分，结帖人nidage_]
本版专家分：11
结帖率 94.12%
CSDN今日推荐
本版专家分：28
本版专家分：11
本版专家分：7008
本版专家分：1500
本版专家分：2180
本版专家分：118
匿名用户不能发表回复！|
其他相关推荐}