It works for me too now, not sure what it was earlier.
Thanks for writing all this down!
Peter
On Sat, Nov 1, 2014 at 12:29 PM, Jens Geyer wrote:
> No prbs here?
>
> -Ursprüngliche Nachricht----- From: Peter Neumark
> Sent: Saturday, November 1, 2014 6:05 PM
> To: dev@th
t should not scare people away.
>
> https://thrift.apache.org/docs/HowToNewLanguage
>
> Thanks + have fun,
> JensG
>
>
>
>
>
--
*Peter Neumark*
DevOps guy @Prezi <http://prezi.com>
Thanks!
On Wed, Oct 15, 2014 at 11:49 PM, Randy Abernethy wrote:
> Thrift is utf-8 everywhere.
>
> The string doc is here: https://thrift.apache.org/docs/types
>
> On Wed, Oct 15, 2014 at 6:53 AM, Peter Neumark
> wrote:
> > Does thrift officially say anything about t
Type numbers go up to 17, including utf8 and 16.
> - Other languages do only define what is actually used, up to 15
>
> I don't know what the intention is/was behind these two additional values.
> Maybe someone else can chime in here.
>
> Have fun,
> JensG
>
>
>
>
wrote:
> Hi Peter,
>
> They need to be interoperable between all platforms an lggs. Somewhere in
> the docs UTF8 is mentioned, IIRC. Is that what you ask for?
>
> ____
> Von: Peter Neumark
> Gesendet: 13.10.2014 22:59
> An: dev@thrift.apach
Sorry, thrift encoding should be string encoding.
On Monday, October 13, 2014, Peter Neumark wrote:
> Hi all,
>
> Looking at the wire format's type IDs, it's clear that thrift supports
> several thrift encodings in it's wire format, yet the IDL does not allow
> o
e each language implementation can choose
the appropriate Unicode type id for encoding strings), or is there some
historical reason for not exposing string encoding options in the thrift
IDL?
Thanks,
Peter
--
*Peter Neumark*
DevOps guy @Prezi <http://prezi.com>
Done: https://github.com/neumark/thrift/compare/THRIFT-2360?expand=1
On Thu, Oct 9, 2014 at 2:03 PM, Roger Meier wrote:
>
> Quoting Peter Neumark :
>
> On Thu, Oct 9, 2014 at 12:49 AM, Roger Meier
>> wrote:
>>
>> Hi Peter
>>>
>>>
On Thu, Oct 9, 2014 at 12:49 AM, Roger Meier
wrote:
> Hi Peter
>
> Quoting Peter Neumark :
>
> Thanks, Roger!
>>
>> I'm also posting this to the dev list, because I think that may be more
>> appropriate than user@.
>>
> Yes, that's why I
ut I'm
crossposting because this seems like a more appropriate forum. Roger Meier
pointed out that there is a patch for a JSON generator, which is very
useful, but it does not in itself allow one to use Thrift as a schema for
JSON messages, which is our goal.
Thanks,
Peter
--
*Peter Neumark*
DevOps guy @Prezi <http://prezi.com>
[
https://issues.apache.org/jira/browse/THRIFT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697120#comment-13697120
]
Peter Neumark commented on THRIFT-1357:
---
JSX is also MIT licensed, and is a
[
https://issues.apache.org/jira/browse/THRIFT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691916#comment-13691916
]
Peter Neumark commented on THRIFT-1357:
---
If you know of a json library tha
[
https://issues.apache.org/jira/browse/THRIFT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Neumark updated THRIFT-1357:
--
Attachment: 0001-Fixed-thrift_json_protocol.erl-to-work-with-JSX-v0.9.patch
My apologies
[
https://issues.apache.org/jira/browse/THRIFT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Neumark updated THRIFT-1357:
--
Attachment: 0001-updated-JSX-version.patch
This patch fixes the compilation issue, which is
Hi!
The issue is not that JSX requires a specific verison of erlang.
Instead, we are faced with the fact that v0.9.0 has a slightly
different interface than what thrift_json_protocol.erl expects.
The attached patch resolves this issue.
As long as we use jsx 0.9.0, the problem should not resurface.
to see some patches in that area!
>
> Regards
> Roger
>
>
>
> Quoting Peter Neumark :
>
> Hi,
>>
>> I've always through its sort of strange to have separate code generators
>> for
>> node.js and browser environments.
>> Since I'm tryi
Hi,
I've always through its sort of strange to have separate code generators for
node.js and browser environments.
Since I'm trying to get the browser to work as a thrift server (responding
to requests coming from the webserver),
I need to use the node.js code generator.
I got a proof of concept
Hi all!
I plan on extending the current javascript thrift libs to allow RPC calls to
be served from the browser.
Through websockets (or socket.io), it is now quite feasible for the
webserver to be the RPC client, and
the browser to be the server. Collaborative web applications like group
chat, sim
attach a
> patch.
>
> On Mon, Jun 27, 2011 at 11:55 AM, Peter Neumark >wrote:
>
> > I have written a thrift json protocol implementation for erlang.
> >
> > My implementation of the protocol may be found here:
> >
> >
> https://github.com/postlock/thrift/
[
https://issues.apache.org/jira/browse/THRIFT-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Neumark updated THRIFT-1227:
--
Attachment: erlang_thrift_json_protocol.patch
The patch containing the JSON protocol
- Library
Affects Versions: 0.7
Environment: Erlang virtual machine (any OS)
Reporter: Peter Neumark
Fix For: 0.7
The attached patch contains an implementation of the thrift JSON protocol in
erlang, along with a modified version of the erlang tutorial which uses the
I have written a thrift json protocol implementation for erlang.
My implementation of the protocol may be found here:
https://github.com/postlock/thrift/blob/trunk/lib/erl/src/thrift_json_protocol.erl
A modified version of the erlang thrift tutorial which uses my
implementation over HTTP to talk
22 matches
Mail list logo
