Possible confusion caused by this github version of portableaserve

[genworks]

Are you dependent upon local changes in this github version of portable aserve?

We now have two divergent hosted projects for this (the original Sourceforge one and your github one), and there does not appear to be any process for synchronizing them. At this point there are several changes which have been made to the Sourceforge version which are not in your github version (and probably vice-versa).

To avoid continued confusion (and especially because the Sourceforge one is the one being carried with Quicklisp), would you consider becoming a committer for the sourceforge version, and returning to using that one (which you normally can do simply by getting it through Quicklisp)?

[fselcukcan]

I have pointed to this Portable AllegroServe from a link when i was looking for info about running Portable AllegroServe on Clozure CL. Now, does Portable AllegroServe on Sourceforge run on Clozure CL? I mean have these projects merged?

[genworks]

The portableaserve hosted on the sourceforge git repository is the most
updated one as far as I know, and should run on all platforms of Clozure CL.

This is the version which is included in Quicklisp (http://quicklisp.org).

The recommended way to get portableaserve loaded is to use Quicklisp:

1. Install Quicklisp according to the instructions at http://quicklisp.org.
2. do: (ql:quickload :aserve)

Best Regards,

Dave

On Thu, Sep 26, 2013 at 7:57 AM, voidcodex notifications@github.com wrote:

I have pointed to this Portable AllegroServe from a link when i was
looking for info about running Portable AllegroServe on Clozure CL. Now,
does Portable AllegroServe on Sourceforge run on Clozure CL? I mean do
these projects merged?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-25161736
.

My Best,

Dave Cooper, Genworks Support
david.cooper@genworks.com, dave.genworks.com(skype)
USA: 248-327-3253(o), 1-248-330-2979(mobile)
UK: 0191 645 1699

[fselcukcan]

Dave, thanks for helpful respond.

[fselcukcan]

About the project on sourceforge, i could not take responses to some of my questions, or to my last Feature Request (about Server Push) in acceptable time delays?
Is it something like abandoned?

Repeating the Feature Request here;
Is it possible to make Server Pushes from Portable AllegroServe, if not, can it be added as a new feature, a feature that seems getting to be a usual http server feature?

I would like to contribute when i come up with a one, but i did not figure out a way to do at the moment.

[genworks]

Thanks for writing.

The project is not abandoned, but I don't think anyone has the bandwidth to
look into http server push at the moment.

This is the first mail I received regarding portableallegroserve. Maybe I
need to update my sourceforge mail settings.

Personally my first priority is to refactor acl-compat to use
now-defacto-standard libraries from quicklisp (eg Bordeaux threads) and to
bring it up to date with franz' original aserve. This should also ease
porting to new platforms like ABCL.

By the way, do you know if Franz' original aserve supports server push? Is
that the same as Websockets?

On Thursday, November 7, 2013, voidcodex wrote:

About the project on sourceforge, i could not take responses to some of my
questions, or to my last Feature Request (about Server Push) in acceptable
time delays?
Is it something like abandoned?

Repeating the Feature Request here;
Is it possible to make Server Pushes from Portable AllegroServe, if not,
can it be added as a new feature, a feature that seems getting to be a
usual http server feature?

I would like to contribute when i come up with a one, but i did not figure
out a way to do at the moment.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27956546
.

My Best,

Dave Cooper, Genworks Support
david.cooper@genworks.com, dave.genworks.com(skype)
USA: 248-327-3253(o), 1-248-330-2979(mobile)
UK: 0191 645 1699

[fselcukcan]

i am not sure about Franz's original having it, i think it does not, i could not see any apparent reference.

with Websockets it can be possible, but the thing is not standardised yet, although the term Websockets is specific to one mechanism, there are other mechanisms that is available and proposed to support the result with various names nowadays some of them are not very specific and are broader terms such as Comet as far as i can see.
Is that kind of communication needs to be initiated by the client again, maybe with background frequent requesting?
are there a way to server to know the client from previous requests, from session info, so no need to make periodic implicit requests to yield the effect?

thanks or immediate response. on source forge i have the same first question that is not answered, if it would be better for the project to continue this messaging there, sourceforge, we can move to there. maybe this way people can join again.